From: Peter Oskolkov <posk@google.com>
To: David Ahern <dsahern@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Peter Oskolkov <posk@posk.io>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next] bpf: fix memory leak in bpf_lwt_xmit_reroute
Date: Mon, 4 Mar 2019 14:37:43 -0800 [thread overview]
Message-ID: <CAPNVh5fmN4LvmeOtzdZ45LK5oVqTKdigPLRiQwBgggexXVbwrg@mail.gmail.com> (raw)
In-Reply-To: <1d2fdd6b-8224-6487-6ba3-1c11875a79a7@gmail.com>
On Mon, Mar 4, 2019 at 1:03 PM David Ahern <dsahern@gmail.com> wrote:
>
> On 3/4/19 1:39 PM, Peter Oskolkov wrote:
> > I found the problem: skb->inner_protocol was not set, so software GSO
> > fallback failed. I have a patch that fixes the issue: IPIP+GRE+TCP
> > gso works! net-next is closed though... Will have to wait for net-next
> > to reopen.
>
> That's a bug fix. I suggest sending now.
I see the encap patches neither in net nor in bpf trees, only in
net-next and bpf-next. And *-next trees are closed, so there is
nowhere to send the fix. Am I missing something?
next prev parent reply other threads:[~2019-03-04 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 6:09 [PATCH bpf-next] bpf: fix memory leak in bpf_lwt_xmit_reroute Peter Oskolkov
2019-02-14 18:11 ` David Ahern
2019-02-14 18:42 ` Peter Oskolkov
2019-02-14 19:10 ` David Ahern
2019-02-14 19:28 ` Peter Oskolkov
[not found] ` <CAPNVh5f_+BdAvoYH6jY7eQ4c4C6qF4-=o0fZ8-nKvvxROuN17Q@mail.gmail.com>
2019-03-02 2:27 ` David Ahern
2019-03-04 2:54 ` Willem de Bruijn
2019-03-04 4:05 ` Willem de Bruijn
2019-03-04 20:39 ` Peter Oskolkov
2019-03-04 21:03 ` David Ahern
2019-03-04 22:37 ` Peter Oskolkov [this message]
2019-03-04 23:28 ` Eric Dumazet
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=CAPNVh5fmN4LvmeOtzdZ45LK5oVqTKdigPLRiQwBgggexXVbwrg@mail.gmail.com \
--to=posk@google.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=posk@posk.io \
--cc=willemdebruijn.kernel@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;
as well as URLs for NNTP newsgroup(s).