From: Feng Tang <feng.tang@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
Igor Zhbanov <i.zhbanov@omprussia.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] driver core: dd: fix return value of __setup handler
Date: Tue, 1 Mar 2022 14:27:56 +0800 [thread overview]
Message-ID: <20220301062756.GJ4548@shbuild999.sh.intel.com> (raw)
In-Reply-To: <20220301041829.15137-1-rdunlap@infradead.org>
Hi Randy,
On Mon, Feb 28, 2022 at 08:18:29PM -0800, Randy Dunlap wrote:
> When "driver_async_probe=nulltty" is used on the kernel boot command line,
> it causes an Unknown parameter message and the string is added to init's
> environment strings, polluting them.
>
> Unknown kernel command line parameters "BOOT_IMAGE=/boot/bzImage-517rc6
> driver_async_probe=nulltty", will be passed to user space.
>
> Run /sbin/init as init process
> with arguments:
> /sbin/init
> with environment:
> HOME=/
> TERM=linux
> BOOT_IMAGE=/boot/bzImage-517rc6
> driver_async_probe=nulltty
>
> Change the return value of the __setup function to 1 to indicate
> that the __setup option has been handled.
Thanks for the fix!
Reviewed-by: Feng Tang <feng.tang@intel.com>
> Fixes: 1ea61b68d0f8 ("async: Add cmdline option to specify drivers to be async probed")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
> Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
> Cc: Feng Tang <feng.tang@intel.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> ---
> drivers/base/dd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20220228.orig/drivers/base/dd.c
> +++ linux-next-20220228/drivers/base/dd.c
> @@ -810,7 +810,7 @@ static int __init save_async_options(cha
> pr_warn("Too long list of driver names for 'driver_async_probe'!\n");
>
> strlcpy(async_probe_drv_names, buf, ASYNC_DRV_NAMES_MAX_LEN);
> - return 0;
> + return 1;
> }
> __setup("driver_async_probe=", save_async_options);
>
prev parent reply other threads:[~2022-03-01 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 4:18 Randy Dunlap
2022-03-01 6:27 ` Feng Tang [this message]
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=20220301062756.GJ4548@shbuild999.sh.intel.com \
--to=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=i.zhbanov@omprussia.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®