From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Alexander Potapenko <glider@google.com>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] ppdev: Distribute switch variables for initialization
Date: Mon, 24 Feb 2020 13:58:58 +0100 [thread overview]
Message-ID: <20200224125858.GA700557@kroah.com> (raw)
In-Reply-To: <20200224123412.bo6e5yfjtinqzhle@debian>
On Mon, Feb 24, 2020 at 12:34:12PM +0000, Sudip Mukherjee wrote:
> On Wed, Feb 19, 2020 at 10:23:11PM -0800, Kees Cook wrote:
> > Variables declared in a switch statement before any case statements
> > cannot be automatically initialized with compiler instrumentation (as
> > they are not part of any execution flow). With GCC's proposed automatic
> > stack variable initialization feature, this triggers a warning (and they
> > don't get initialized). Clang's automatic stack variable initialization
> > (via CONFIG_INIT_STACK_ALL=y) doesn't throw a warning, but it also
> > doesn't initialize such variables[1]. Note that these warnings (or silent
> > skipping) happen before the dead-store elimination optimization phase,
> > so even when the automatic initializations are later elided in favor of
> > direct initializations, the warnings remain.
> >
> > To avoid these problems, move such variables into the "case" where
> > they're used or lift them up into the main function body.
> >
> > drivers/char/ppdev.c: In function ‘pp_do_ioctl’:
> > drivers/char/ppdev.c:516:25: warning: statement will never be executed [-Wswitch-unreachable]
> > 516 | struct ieee1284_info *info;
> > | ^~~~
> >
> > [1] https://bugs.llvm.org/show_bug.cgi?id=44916
> >
> > Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Acked-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
>
> Greg, Can you please take it in your tree...
Already taken :)
prev parent reply other threads:[~2020-02-24 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 6:23 Kees Cook
2020-02-24 12:34 ` Sudip Mukherjee
2020-02-24 12:58 ` Greg Kroah-Hartman [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=20200224125858.GA700557@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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 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®