From: Chris Down <chris@chrisdown.name>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jessica Yu <jeyu@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
YueHaibing <yuehaibing@huawei.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] printk: avoid -Wsometimes-uninitialized warning
Date: Mon, 27 Sep 2021 14:19:18 +0100 [thread overview]
Message-ID: <YVHE1qclD6ZyjvvD@chrisdown.name> (raw)
In-Reply-To: <20210927125007.1581919-1-arnd@kernel.org>
Hi Arnd,
Arnd Bergmann writes:
>From: Arnd Bergmann <arnd@arndb.de>
>
>clang notices that the pi_get_entry() function would use
>uninitialized data if it was called with a non-NULL module
>pointer on a kernel that does not support modules:
On a !CONFIG_MODULES kernel, we _never_ pass a non-NULL module pointer. This
isn't just convention: we don't even have `struct module` fully fleshed out, so
it technically cannot be so.
>kernel/printk/index.c:32:6: error: variable 'nr_entries' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
> if (!mod) {
> ^~~~
>kernel/printk/index.c:38:13: note: uninitialized use occurs here
> if (pos >= nr_entries)
> ^~~~~~~~~~
>kernel/printk/index.c:32:2: note: remove the 'if' if its condition is always true
> if (!mod) {
>
>Rework the condition to make it clear to the compiler that we are always
>in the second case. Unfortunately the #ifdef is still required as the
>definition of 'struct module' is hidden when modules are disabled.
Having IS_ENABLED and then an #ifdef seems to hurt code readability to me.
>Fixes: 337015573718 ("printk: Userspace format indexing support")
Does this really fix anything, or just clang's ignorance? If the latter, clang
needs to be smarter here: as far as I can see there are no occasions where
there's even any opportunity for a non-NULL pointer to come in on a
!CONFIG_MODULES kernel, since `struct module` isn't even complete.
>Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>---
> kernel/printk/index.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
>diff --git a/kernel/printk/index.c b/kernel/printk/index.c
>index d3709408debe..b4d90bab6d4d 100644
>--- a/kernel/printk/index.c
>+++ b/kernel/printk/index.c
>@@ -22,14 +22,12 @@ static struct pi_entry *pi_get_entry(const struct module *mod, loff_t pos)
> struct pi_entry **entries;
> unsigned int nr_entries;
>
>+ if (IS_ENABLED(CONFIG_MODULES) && mod) {
> #ifdef CONFIG_MODULES
>- if (mod) {
> entries = mod->printk_index_start;
> nr_entries = mod->printk_index_size;
>- }
> #endif
>-
>- if (!mod) {
>+ } else {
> /* vmlinux, comes from linker symbols */
> entries = __start_printk_index;
> nr_entries = __stop_printk_index - __start_printk_index;
>--
>2.29.2
>
next prev parent reply other threads:[~2021-09-27 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 12:49 [PATCH] printk: avoid -Wsometimes-uninitialized warning Arnd Bergmann
2021-09-27 13:19 ` Chris Down [this message]
2021-09-27 13:28 ` Arnd Bergmann
2021-09-27 13:33 ` Chris Down
2021-09-27 13:38 ` Chris Down
2021-09-27 16:21 ` Steven Rostedt
2021-09-27 18:32 ` Arnd Bergmann
2021-09-27 21:58 ` Steven Rostedt
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=YVHE1qclD6ZyjvvD@chrisdown.name \
--to=chris@chrisdown.name \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jeyu@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=yuehaibing@huawei.com \
/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.