aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorGlauber Costa <[email protected]>2013-02-04 14:28:49 -0800
committerLinus Torvalds <[email protected]>2013-02-05 20:38:48 +1100
commit91c777d86752b00bb3a1d8efa3d8f7e1264f38a9 (patch)
treebb9f3340c8109da5c29e57608f205e97a5f0e03d /tools/perf/util/scripting-engines/trace-event-python.c
parent631b0cfdbd801ceae8762e8d287f15da26792ebe (diff)
memcg: fix typo in kmemcg cache walk macro
The macro for_each_memcg_cache_index contains a silly yet potentially deadly mistake. Although the macro parameter is _idx, the loop tests are done over i, not _idx. This hasn't generated any problems so far, because all users use i as a loop index. However, while playing with an extension of the code I ended using another loop index and the compiler was quick to complain. Unfortunately, this is not the kind of thing that testing reveals =( Signed-off-by: Glauber Costa <[email protected]> Cc: Kamezawa Hiroyuki <[email protected]> Cc: Johannes Weiner <[email protected]> Acked-by: Michal Hocko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions