Netdev List
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: David Binderman <dcb314@hotmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	"ast@kernel.org" <ast@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel/bpf/verifier.c: 4 * possible unintended fallthrough ?
Date: Tue, 20 Dec 2016 13:28:43 -0500	[thread overview]
Message-ID: <1482258523.24490.10@smtp.office365.com> (raw)
In-Reply-To: <VI1PR08MB10228EE1E2FA0EBFEA78DE919C900@VI1PR08MB1022.eurprd08.prod.outlook .com>

On Tue, Dec 20, 2016 at 11:34 AM, David Binderman <dcb314@hotmail.com> 
wrote:
> 
> Hello there,
> 
>> From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
>> I've tried 4.9 and 5.2 and don't see this warning.
> 
> As expected - I used a development version of gcc.
> Latest released version is 6.2
> 
>> Is this 6.x gcc?
> 
> 7.0 would be more accurate.
> 
>> I suspect it will have such warnings all over the kernel.
> 
> Indeed it has hundreds, but the subject under discussion is file
> kernel/bpf/verifier.c.
> 
> I am still not sure if I have found a fallthrough bug or not.

You haven't, this is intended so is a useless warning.  Thanks,

Josef

      parent reply	other threads:[~2016-12-20 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR08MB102286884ADF02FB45C203109C900@VI1PR08MB1022.eurprd08.prod.outlook.com>
2016-12-20 16:17 ` kernel/bpf/verifier.c: 4 * possible unintended fallthrough ? Alexei Starovoitov
     [not found]   ` <VI1PR08MB10228EE1E2FA0EBFEA78DE919C900@VI1PR08MB1022.eurprd08.prod.outlook.com>
     [not found]     ` <VI1PR08MB10228EE1E2FA0EBFEA78DE919C900@VI1PR08MB1022.eurprd08.prod.outlook .com>
2016-12-20 18:28       ` Josef Bacik [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=1482258523.24490.10@smtp.office365.com \
    --to=jbacik@fb.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=dcb314@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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