diff options
| author | KOSAKI Motohiro <[email protected]> | 2010-08-09 17:19:37 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2010-08-09 20:45:01 -0700 |
| commit | 26ebc984913b6a8d86d724b3a79d2ed4ed574612 (patch) | |
| tree | 9d293c6f8b1bc5120beaa173590dcd83cd0e2eb0 /tools/perf/scripts/python | |
| parent | f88ccad5886d5a864b8b0d48c666ee9998dec53f (diff) | |
oom: /proc/<pid>/oom_score treat kernel thread honestly
If a kernel thread is using use_mm(), badness() returns a positive value.
This is not a big issue because caller take care of it correctly. But
there is one exception, /proc/<pid>/oom_score calls badness() directly and
doesn't care that the task is a regular process.
Another example, /proc/1/oom_score return !0 value. But it's unkillable.
This incorrectness makes administration a little confusing.
This patch fixes it.
Signed-off-by: KOSAKI Motohiro <[email protected]>
Cc: Minchan Kim <[email protected]>
Cc: David Rientjes <[email protected]>
Cc: KAMEZAWA Hiroyuki <[email protected]>
Cc: Oleg Nesterov <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions