summaryrefslogtreecommitdiffstats
path: root/arch/sh/kernel/vsyscall
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@redhat.com>2012-03-23 23:02:50 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2012-03-24 00:58:42 +0100
commit1cc684ab75123efe7ff446eb821d44375ba8fa30 (patch)
tree165069093fc048b979ed38e537b19febdc7889d3 /arch/sh/kernel/vsyscall
parentkmod: introduce call_modprobe() helper (diff)
downloadlinux-1cc684ab75123efe7ff446eb821d44375ba8fa30.tar.xz
linux-1cc684ab75123efe7ff446eb821d44375ba8fa30.zip
kmod: make __request_module() killable
As Tetsuo Handa pointed out, request_module() can stress the system while the oom-killed caller sleeps in TASK_UNINTERRUPTIBLE. The task T uses "almost all" memory, then it does something which triggers request_module(). Say, it can simply call sys_socket(). This in turn needs more memory and leads to OOM. oom-killer correctly chooses T and kills it, but this can't help because it sleeps in TASK_UNINTERRUPTIBLE and after that oom-killer becomes "disabled" by the TIF_MEMDIE task T. Make __request_module() killable. The only necessary change is that call_modprobe() should kmalloc argv and module_name, they can't live in the stack if we use UMH_KILLABLE. This memory is freed via call_usermodehelper_freeinfo()->cleanup. Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Signed-off-by: Oleg Nesterov <oleg@redhat.com> Cc: Rusty Russell <rusty@rustcorp.com.au> Cc: Tejun Heo <tj@kernel.org> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/sh/kernel/vsyscall')
0 files changed, 0 insertions, 0 deletions