public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	arjan@linux.intel.com, alan@lxorguk.ukuu.org.uk,
	viro@ZenIV.linux.org.uk, jmorris@namei.org,
	akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: Please revert kobject_uevent UMH_NO_WAIT
Date: Thu, 16 Apr 2009 14:24:36 -0700	[thread overview]
Message-ID: <20090416212436.GA31113@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0904162145130.645@blonde.anvils>

On Thu, Apr 16, 2009 at 09:55:29PM +0100, Hugh Dickins wrote:
> Please revert commit f520360d93cdc37de5d972dac4bf3bdef6a7f6a7
> "kobject: don't block for each kobject_uevent".
> 
> Tetsuo Handa, running a kernel with CONFIG_DEBUG_PAGEALLOC=y
> and CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug, has been hitting RCU
> detected CPU stalls: it's been spinning in the loop where do_execve()
> counts up the args (but why wasn't fixup_exception working? dunno).
> 
> The recent change, switching kobject_uevent_env() from UMH_WAIT_EXEC
> to UMH_NO_WAIT, is broken: the exec uses args on the local stack here,
> and an env which is kfreed as soon as call_usermodehelper() returns.
> It very much needs to wait for the exec to be done.
> 
> Or keep the UMH_NO_WAIT, and complicate the code to allocate and free
> these resources correctly?  No, as GregKH pointed out when making the
> commit, CONFIG_UEVENT_HELPER_PATH="" is a much better optimization -
> though some distros are still saying /sbin/hotplug in their .config,
> yet with no such binary in their initrd or their root.
> 
> Or...
> 
> [PATCH] revert kobject_uevent UMH_NO_WAIT
> 
> Reported-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Signed-off-by: Hugh Dickins <hugh@veritas.com>

Acked-by: Greg Kroah-Hartman <gregkh@suse.de>

Linus, I can do this in a tree of patches to send to you or you can do it
yourself, which ever is easier.

thanks,

greg k-h

  parent reply	other threads:[~2009-04-16 21:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  0:57 [2.6.30-rc1] RCU detected CPU 1 stall Tetsuo Handa
2009-04-10 14:22 ` Paul E. McKenney
2009-04-10 15:03   ` Al Viro
2009-04-10 15:32     ` Paul E. McKenney
2009-04-10 21:08       ` Tetsuo Handa
2009-04-10 23:12         ` Paul E. McKenney
2009-04-10 23:39           ` Al Viro
2009-04-11  0:48             ` Paul E. McKenney
2009-04-13  0:48             ` Tetsuo Handa
2009-04-13 19:55               ` Paul E. McKenney
2009-04-13 21:31                 ` Tetsuo Handa
2009-04-13 22:47                   ` Paul E. McKenney
2009-04-14 17:11               ` Hugh Dickins
2009-04-15  3:28                 ` Tetsuo Handa
2009-04-15 20:34                   ` Hugh Dickins
2009-04-16  0:46                     ` Tetsuo Handa
2009-04-16  5:15                       ` Hugh Dickins
2009-04-16  5:35                         ` Tetsuo Handa
2009-04-16 20:37                           ` Greg KH
2009-04-16 20:55                           ` Please revert kobject_uevent UMH_NO_WAIT Hugh Dickins
2009-04-16 20:58                             ` [PATCH] mm: pass correct mm when growing stack Hugh Dickins
2009-04-16 21:24                             ` Greg KH [this message]
2009-04-16 21:30                               ` Please revert kobject_uevent UMH_NO_WAIT Arjan van de Ven
2009-04-16 21:36                                 ` Will Newton

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=20090416212436.GA31113@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@linux.intel.com \
    --cc=hugh@veritas.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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