From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Arnd Bergmann <arnd@arndb.de>,
Randy Dunlap <rdunlap@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devcoredump: avoid -Wempty-body warnings
Date: Mon, 22 Mar 2021 11:29:27 +0100 [thread overview]
Message-ID: <YFhxhyXLyTqp4ppH@kroah.com> (raw)
In-Reply-To: <20210322102002.28990-1-arnd@kernel.org>
On Mon, Mar 22, 2021 at 11:19:53AM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Cleaning out the last -Wempty-body warnings found some interesting
> cases with empty macros, along with harmless warnings like this one:
>
> drivers/base/devcoredump.c: In function 'dev_coredumpm':
> drivers/base/devcoredump.c:297:56: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body]
> 297 | /* nothing - symlink will be missing */;
> | ^
> drivers/base/devcoredump.c:301:56: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body]
> 301 | /* nothing - symlink will be missing */;
> | ^
>
> Randy tried addressing this one before, and there were multiple
> other ideas in that thread.
>
> Pick up the one that Matthew Wilcox suggested by adding a
> WARN_ON_ONCE() and a comment.
>
> Link: https://lore.kernel.org/lkml/20200418184111.13401-8-rdunlap@infradead.org/
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/base/devcoredump.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/base/devcoredump.c b/drivers/base/devcoredump.c
> index 9243468e2c99..88e0d931439e 100644
> --- a/drivers/base/devcoredump.c
> +++ b/drivers/base/devcoredump.c
> @@ -292,13 +292,16 @@ void dev_coredumpm(struct device *dev, struct module *owner,
> if (device_add(&devcd->devcd_dev))
> goto put_device;
>
> - if (sysfs_create_link(&devcd->devcd_dev.kobj, &dev->kobj,
> - "failing_device"))
> - /* nothing - symlink will be missing */;
> + /*
> + * These should normally not fail, but there is no problem
> + * continuing without the links, so just warn instead of
> + * failing.
> + */
> + WARN_ON_ONCE(sysfs_create_link(&devcd->devcd_dev.kobj, &dev->kobj,
> + "failing_device"));
>
> - if (sysfs_create_link(&dev->kobj, &devcd->devcd_dev.kobj,
> - "devcoredump"))
> - /* nothing - symlink will be missing */;
> + WARN_ON_ONCE(sysfs_create_link(&dev->kobj, &devcd->devcd_dev.kobj,
> + "devcoredump"));
We do not want to reboot machines that have panic-on-warn set, so if
this really needs a trace dump, please do that instead...
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-22 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:19 [PATCH] devcoredump: avoid -Wempty-body warnings Arnd Bergmann
2021-03-22 10:29 ` Greg Kroah-Hartman [this message]
2021-03-22 11:22 ` Arnd Bergmann
2021-03-22 11:35 ` Greg Kroah-Hartman
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=YFhxhyXLyTqp4ppH@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=joe@perches.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=willy@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