From: Alexei Starovoitov <ast@plumgrid.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
"Devon H. O'Dell" <dho@fastly.com>,
davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf, skb_do_redirect: clear sender_cpu before xmit
Date: Fri, 9 Oct 2015 21:55:58 -0700 [thread overview]
Message-ID: <56189A5E.7010405@plumgrid.com> (raw)
In-Reply-To: <1444451914.27760.116.camel@edumazet-glaptop2.roam.corp.google.com>
On 10/9/15 9:38 PM, Eric Dumazet wrote:
> On Fri, 2015-10-09 at 20:19 -0700, Alexei Starovoitov wrote:
>
>> since this bug wasn't fixed at once in all places, it means
>> that it is hard to review _all_ needed call-sites.
>> There are 7 places that call skb_sender_cpu_clear() in net-next.
>> Plus 2 more in net.
>> How many such paths from rx to tx left?
>> On the first glance ovs is missing one and who knows what else.
>
> Alexei, what's happening ?
>
> The original patch is 6 months old. If this issue was so urgent, how
> comes it took so long to catch the remaining bugs ?
no urgency at all. bpf side is clean, so I'm not worried :)
> Just add skb_sender_cpu_clear() where needed, thanks.
>
> Using union is hard, but there is a price to performance.
>
> skb size is absolutely critical and deserves some headaches.
yep. as I said it shouldn't be increased and proposed in-band sign bit.
Anyway, since you and Daniel are ok with adding skb_sender_cpu_clear()
in other places, I rest my case.
next prev parent reply other threads:[~2015-10-10 4:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 8:16 [PATCH net-next] bpf, skb_do_redirect: clear sender_cpu before xmit Daniel Borkmann
2015-10-07 15:46 ` Alexei Starovoitov
2015-10-09 0:50 ` Devon H. O'Dell
2015-10-09 2:35 ` Alexei Starovoitov
2015-10-09 16:40 ` Devon H. O'Dell
2015-10-10 3:11 ` Alexei Starovoitov
2015-10-09 17:33 ` Daniel Borkmann
2015-10-10 3:19 ` Alexei Starovoitov
2015-10-10 4:38 ` Eric Dumazet
2015-10-10 4:55 ` Alexei Starovoitov [this message]
2015-10-10 4:56 ` Alexei Starovoitov
2015-10-10 17:12 ` Eric Dumazet
2015-11-16 18:07 ` Eric Dumazet
2015-10-08 12:07 ` 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=56189A5E.7010405@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dho@fastly.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).