From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: oleg@redhat.com, tj@kernel.org
Cc: rusty@rustcorp.com.au, akpm@linux-foundation.org,
arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to-mm tree
Date: Sat, 4 Feb 2012 21:56:49 +0900 [thread overview]
Message-ID: <201202042156.HCJ57836.OQMFSVJHLtFOFO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20120203180030.GA8842@redhat.com>
Oleg Nesterov wrote:
> What do you think about s/khelper/system/ instead of this patch?
I'm not catching up with this topic. But I'm fine with any solution provided
that it can handle
some kernel function calls request_module()
request_module() triggers call_usermodehelper("/sbin/modprobe", UMH_WAIT_PROC)
/sbin/modprobe loads a kernel module
loading a kernel module triggers kobject_uevent_env()
kobject_uevent_env() calls call_usermodehelper("/sbin/hotplug", UMH_WAIT_EXEC)
do_execve("/sbin/hotplug") calls request_module("binfmt-0000")
request_module("binfmt-0000") triggers call_usermodehelper("/sbin/modprobe", UMH_WAIT_PROC)
/sbin/modprobe fails to load binfmt-0000 module
call trace on an UP machine.
kmod-avoid-deadlock-by-recursive-kmod-call.patch is for avoiding
call_usermodehelper("/sbin/modprobe", UMH_WAIT_PROC) called from
call_usermodehelper("/sbin/hotplug", UMH_WAIT_EXEC).
next prev parent reply other threads:[~2012-02-04 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:56 + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to -mm tree Oleg Nesterov
2012-01-27 2:55 ` Rusty Russell
2012-01-27 14:32 ` Oleg Nesterov
2012-01-29 0:49 ` Rusty Russell
2012-01-29 16:31 ` Oleg Nesterov
2012-01-29 23:26 ` Rusty Russell
2012-01-30 0:25 ` Tejun Heo
2012-01-30 13:03 ` Oleg Nesterov
2012-01-30 17:28 ` Tejun Heo
2012-02-03 18:00 ` Oleg Nesterov
2012-02-03 19:26 ` Tejun Heo
2012-02-04 12:56 ` Tetsuo Handa [this message]
2012-02-06 17:19 ` + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to-mm tree Oleg Nesterov
2012-01-30 12:38 ` + kmod-avoid-deadlock-by-recursive-kmod-call.patch added to -mm tree Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201202042156.HCJ57836.OQMFSVJHLtFOFO@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).