diff options
author | Oleg Nesterov <oleg@redhat.com> | 2012-03-23 15:02:50 -0700 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2013-03-06 03:24:28 +0000 |
commit | d0820f8020fa87d9e0433b062fca2b7206e0cd11 (patch) | |
tree | daf7f76eb17112151d4883ce57103877e2441532 /include | |
parent | 95b467ca30d2e56c08fbe541a02318470457cca7 (diff) | |
download | kernel-common-d0820f8020fa87d9e0433b062fca2b7206e0cd11.tar.gz kernel-common-d0820f8020fa87d9e0433b062fca2b7206e0cd11.tar.bz2 kernel-common-d0820f8020fa87d9e0433b062fca2b7206e0cd11.zip |
kmod: make __request_module() killable
commit 1cc684ab75123efe7ff446eb821d44375ba8fa30 upstream.
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>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions