From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
hare@suse.de, "Luis R. Rodriguez" <mcgrof@suse.com>,
"4.2+" <stable@vger.kernel.org>
Subject: Re: [PATCH RESEND] driver-core: fix modparam async_probe request
Date: Sat, 16 Jan 2016 11:05:50 -0800 [thread overview]
Message-ID: <20160116190550.GF9203@dtor-ws> (raw)
In-Reply-To: <1452901337-27267-1-git-send-email-mcgrof@do-not-panic.com>
Hi Luis,
On Fri, Jan 15, 2016 at 03:42:17PM -0800, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> Commit f2411da746985 ("driver-core: add driver module
> asynchronous probe support") added async probe support,
> in two forms:
>
> * in-kernel driver specification annotation
> * generic async_probe module parameter (modprobe foo async_probe)
>
> To support the generic kernel parameter parse_args() was
> extended via commit ecc8617053e0 ("module: add extra
> argument for parse_params() callback") however commit
> failed to f2411da746985 failed to add the required argument.
>
> This causes a crash then whenever async_probe generic
> module parameter is used. This was overlooked when the
> form in which in-kernel async probe support was reworked
> a bit... Fix this as originally intended.
>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: stable@vger.kernel.org (4.2+)
> Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
> ---
>
> Resending and addressing Rusty, the other patch I sent on Dec 19
> was addressed to Greg by mistake. Sorry about that.
>
> kernel/module.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 8f051a106676..88100ea77c55 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3402,16 +3402,22 @@ out:
> static int unknown_module_param_cb(char *param, char *val, const char *modname,
> void *arg)
> {
> - struct module *mod = arg;
> + struct module *mod;
> int ret;
>
> if (strcmp(param, "async_probe") == 0) {
> + mod = arg;
> + if (!mod) {
> + ret = -ENOENT;
> + goto out;
> + }
Why do we need this chunk? We only call unknown_module_param_cb() from
one place and with your chunk below we do know that "mod" is never NULL.
> mod->async_probe_requested = true;
> return 0;
> }
>
> /* Check for magic 'dyndbg' arg */
> ret = ddebug_dyndbg_module_param_cb(param, val, modname);
> +out:
> if (ret != 0)
> pr_warn("%s: unknown parameter '%s' ignored\n", modname, param);
> return 0;
> @@ -3515,7 +3521,7 @@ static int load_module(struct load_info *info, const char __user *uargs,
>
> /* Module is ready to execute: parsing args may do that. */
> after_dashes = parse_args(mod->name, mod->args, mod->kp, mod->num_kp,
> - -32768, 32767, NULL,
> + -32768, 32767, mod,
I believe this is the only change that is needed.
> unknown_module_param_cb);
> if (IS_ERR(after_dashes)) {
> err = PTR_ERR(after_dashes);
> --
> 2.6.2
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-01-16 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 23:42 [PATCH RESEND] driver-core: fix modparam async_probe request Luis R. Rodriguez
2016-01-16 19:05 ` Dmitry Torokhov [this message]
2016-01-16 21:21 ` Luis R. Rodriguez
2016-01-19 2:37 ` Rusty Russell
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=20160116190550.GF9203@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.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