All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] call_usermodehelper_setup() should use GFP_KERNEL
Date: Fri, 09 May 2008 00:53:49 +0100	[thread overview]
Message-ID: <4823928D.7080907@goop.org> (raw)
In-Reply-To: <20080509084248.43B5.KOSAKI.MOTOHIRO@jp.fujitsu.com>

KOSAKI Motohiro wrote:
> UMH_WAIT_EXEC and UMH_WAIT_PROC mean wait on finish of exec or process exit.
> I can't imagine situation that exec is waitable *and* allocate isn't waitable.
>   

Yeah, that's why I was asking about UMH_NO_WAIT, where the caller may 
not want to wait, but the context would allow the allocation to block if 
necessary.

    J

  reply	other threads:[~2008-05-08 23:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  6:41 [PATCH] call_usermodehelper_setup() should use GFP_KERNEL KOSAKI Motohiro
2008-05-08  7:23 ` Li Zefan
2008-05-08  7:31   ` KOSAKI Motohiro
2008-05-08  8:29     ` Andrew Morton
2008-05-08  9:40       ` KOSAKI Motohiro
2008-05-08 10:16       ` Jeremy Fitzhardinge
2008-05-08 10:38         ` KOSAKI Motohiro
2008-05-08 12:58           ` Jeremy Fitzhardinge
2008-05-08 23:46             ` KOSAKI Motohiro
2008-05-08 23:53               ` Jeremy Fitzhardinge [this message]
2008-05-09  0:04                 ` KOSAKI Motohiro
2008-05-09  0:08                   ` Jeremy Fitzhardinge

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=4823928D.7080907@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=jeremy@xensource.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.