From: Oleg Nesterov <oleg@redhat.com>
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: lucas.de.marchi@gmail.com, David Howells <dhowells@redhat.com>,
James Morris <james.l.morris@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] kmod: split call to call_usermodehelper_fns()
Date: Sat, 9 Mar 2013 21:23:29 +0100 [thread overview]
Message-ID: <20130309202329.GC16399@redhat.com> (raw)
In-Reply-To: <1362723313-839-4-git-send-email-lucas.demarchi@profusion.mobi>
On 03/08, Lucas De Marchi wrote:
>
> Use call_usermodehelper_setup() + call_usermodehelper_exec() instead of
> calling call_usermodehelper_fns(). In case the latter returns -ENOMEM
> the cleanup function may had not been called - in this case we would
> not free argv and module_name.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Thanks!
looks correct, but...
> @@ -98,8 +100,17 @@ static int call_modprobe(char *module_name, int wait)
> argv[3] = module_name; /* check free_modprobe_argv() */
> argv[4] = NULL;
>
> - return call_usermodehelper_fns(modprobe_path, argv, envp,
> - wait | UMH_KILLABLE, NULL, free_modprobe_argv, NULL);
> + gfp_mask = (wait == UMH_NO_WAIT) ? GFP_ATOMIC : GFP_KERNEL;
Why? it is never called with UMH_NO_WAIT,
> + info = call_usermodehelper_setup(modprobe_path, argv, envp,
> + gfp_mask, NULL, free_modprobe_argv,
can't we simply use GFP_KERNEL?
Oleg.
next prev parent reply other threads:[~2013-03-09 20:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 6:15 [PATCH v2 0/7] kmod/usermodehelper changes Lucas De Marchi
2013-03-08 6:15 ` [PATCH v2 1/7] kernel/sys.c: Use the simpler call_usermodehelper() Lucas De Marchi
2013-03-09 20:17 ` Oleg Nesterov
2013-03-08 6:15 ` [PATCH v2 2/7] usermodehelper: Export _exec() and _setup() functions Lucas De Marchi
2013-03-09 20:21 ` Oleg Nesterov
2013-03-08 6:15 ` [PATCH v2 3/7] kmod: split call to call_usermodehelper_fns() Lucas De Marchi
2013-03-09 20:23 ` Oleg Nesterov [this message]
2013-03-09 23:54 ` Lucas De Marchi
2013-03-08 6:15 ` [PATCH v2 4/7] KEYS: " Lucas De Marchi
2013-03-09 20:25 ` Oleg Nesterov
2013-03-09 23:55 ` Lucas De Marchi
2013-03-25 12:55 ` David Howells
2013-03-25 13:11 ` Lucas De Marchi
2013-03-08 6:15 ` [PATCH v2 5/7] coredump: remove trailling whitespaces Lucas De Marchi
2013-03-08 6:15 ` [PATCH v2 6/7] Split remaining calls to call_usermodehelper_fns() Lucas De Marchi
2013-03-09 20:42 ` Oleg Nesterov
2013-03-09 23:57 ` Lucas De Marchi
2013-03-08 6:15 ` [PATCH v2 7/7] kmod: remove call_usermodehelper_fns() Lucas De Marchi
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=20130309202329.GC16399@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@profusion.mobi \
/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