mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lawrence Brakmo <brakmo@fb.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Colin King <colin.king@canonical.com>,
	Alexei Starovoitov <ast@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][bpf-next] bpf: add missing break in for the TCP_BPF_SNDCWND_CLAMP case
Date: Tue, 4 Jul 2017 18:26:34 +0000	[thread overview]
Message-ID: <385C64DB-4BF4-4AC1-B7F0-76AB30969682@fb.com> (raw)
In-Reply-To: <595BB3AF.3000304@iogearbox.net>



On 7/4/17, 8:26 AM, "netdev-owner@vger.kernel.org on behalf of Daniel Borkmann" <netdev-owner@vger.kernel.org on behalf of daniel@iogearbox.net> wrote:

    [ +Lawrence ]
    
    On 07/04/2017 05:21 PM, Colin King wrote:
    > From: Colin Ian King <colin.king@canonical.com>
    >
    > There appears to be a missing break in the TCP_BPF_SNDCWND_CLAMP case.
    > Currently the non-error path where val is greater than zero falls through
    > to the default case that sets the error return to -EINVAL. Add in
    > the missing break.
    >
    > Detected by CoverityScan, CID#1449376 ("Missing break in switch")
    >
    > Fixes: 13bf96411ad2 ("bpf: Adds support for setting sndcwnd clamp")
    > Signed-off-by: Colin Ian King <colin.king@canonical.com>
    
    Acked-by: Daniel Borkmann daniel@iogearbox.net
Acked-by: Lawrence Brakmo <brakmo@fb.com>
    
    > ---
    >   net/core/filter.c | 1 +
    >   1 file changed, 1 insertion(+)
    >
    > diff --git a/net/core/filter.c b/net/core/filter.c
    > index 94169572d002..c7f737058d89 100644
    > --- a/net/core/filter.c
    > +++ b/net/core/filter.c
    > @@ -2867,6 +2867,7 @@ BPF_CALL_5(bpf_setsockopt, struct bpf_sock_ops_kern *, bpf_sock,
    >   					tp->snd_cwnd_clamp = val;
    >   					tp->snd_ssthresh = val;
    >   				}
    > +				break;
    >   			default:
    >   				ret = -EINVAL;
    >   			}
    >
    
    

  reply	other threads:[~2017-07-04 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 15:21 Colin King
2017-07-04 15:26 ` Daniel Borkmann
2017-07-04 18:26   ` Lawrence Brakmo [this message]
2017-07-05  8:09 ` David Miller

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=385C64DB-4BF4-4AC1-B7F0-76AB30969682@fb.com \
    --to=brakmo@fb.com \
    --cc=ast@kernel.org \
    --cc=colin.king@canonical.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernel-janitors@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®