diff options
| author | Johannes Weiner <[email protected]> | 2013-10-31 16:34:13 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2013-10-31 16:58:13 -0700 |
| commit | 3168ecbe1c04ec3feb7cb42388a17d7f047fe1a2 (patch) | |
| tree | b8e0a03d787c2219b1d1fd833193de7abc59442e /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 12aee278b50c4a94a93fa0b4d201ae35d792c696 (diff) | |
mm: memcg: use proper memcg in limit bypass
Commit 84235de394d9 ("fs: buffer: move allocation failure loop into the
allocator") allowed __GFP_NOFAIL allocations to bypass the limit if they
fail to reclaim enough memory for the charge. But because the main test
case was on a 3.2-based system, the patch missed the fact that on newer
kernels the charge function needs to return root_mem_cgroup when
bypassing the limit, and not NULL. This will corrupt whatever memory is
at NULL + percpu pointer offset. Fix this quickly before problems are
reported.
Signed-off-by: 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