linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Jeff Layton <jlayton@kernel.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Jens Axboe <axboe@kernel.dk>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Alexander Potapenko <glider@google.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fcntl: Distribute switch variables for initialization
Date: Mon, 2 Mar 2020 20:41:34 -0800	[thread overview]
Message-ID: <202003022040.40A32072@keescook> (raw)
In-Reply-To: <20200220062243.68809-1-keescook@chromium.org>

On Wed, Feb 19, 2020 at 10:22:43PM -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.
> 
> fs/fcntl.c: In function ‘send_sigio_to_task’:
> fs/fcntl.c:738:20: warning: statement will never be executed [-Wswitch-unreachable]
>   738 |   kernel_siginfo_t si;
>       |                    ^~
> 
> [1] https://bugs.llvm.org/show_bug.cgi?id=44916
> 
> Signed-off-by: Kees Cook <keescook@chromium.org>

Ping. Can someone pick this up, please?

Thanks!

-Kees

> ---
>  fs/fcntl.c |    6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/fcntl.c b/fs/fcntl.c
> index 9bc167562ee8..2e4c0fa2074b 100644
> --- a/fs/fcntl.c
> +++ b/fs/fcntl.c
> @@ -735,8 +735,9 @@ static void send_sigio_to_task(struct task_struct *p,
>  		return;
>  
>  	switch (signum) {
> -		kernel_siginfo_t si;
> -		default:
> +		default: {
> +			kernel_siginfo_t si;
> +
>  			/* Queue a rt signal with the appropriate fd as its
>  			   value.  We use SI_SIGIO as the source, not 
>  			   SI_KERNEL, since kernel signals always get 
> @@ -769,6 +770,7 @@ static void send_sigio_to_task(struct task_struct *p,
>  			si.si_fd    = fd;
>  			if (!do_send_sig_info(signum, &si, p, type))
>  				break;
> +		}
>  		/* fall-through - fall back on the old plain SIGIO signal */
>  		case 0:
>  			do_send_sig_info(SIGIO, SEND_SIG_PRIV, p, type);
> 

-- 
Kees Cook

  reply	other threads:[~2020-03-03  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  6:22 [PATCH] fcntl: Distribute switch variables for initialization Kees Cook
2020-03-03  4:41 ` Kees Cook [this message]
2020-03-03 15:55   ` Jeff Layton
2020-03-03 21:11     ` Kees Cook

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=202003022040.40A32072@keescook \
    --to=keescook@chromium.org \
    --cc=axboe@kernel.dk \
    --cc=bfields@fieldses.org \
    --cc=glider@google.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).