bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"David S . Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Stanislav Fomichev <sdf@google.com>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf 0/2] bpf: gso_segs fixes
Date: Tue, 23 Jul 2019 14:15:36 -0700	[thread overview]
Message-ID: <CAADnVQLZoTTcD11V69snu6=SHgLUW97tenHrcCa2w_3gmw=29Q@mail.gmail.com> (raw)
In-Reply-To: <20190723101538.136328-1-edumazet@google.com>

On Tue, Jul 23, 2019 at 3:15 AM Eric Dumazet <edumazet@google.com> wrote:
> First patch changes the kernel, second patch
> adds a new test.
> Note that other patches might be needed to take
> care of similar issues in sock_ops_convert_ctx_access()

Nice catch!
Applied to bpf tree. Thanks

      parent reply	other threads:[~2019-07-23 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 10:15 [PATCH bpf 0/2] bpf: gso_segs fixes Eric Dumazet
2019-07-23 10:15 ` [PATCH bpf 1/2] bpf: fix access to skb_shared_info->gso_segs Eric Dumazet
2019-07-23 10:15 ` [PATCH bpf 2/2] selftests/bpf: add another gso_segs access Eric Dumazet
2019-07-23 21:15 ` Alexei Starovoitov [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAADnVQLZoTTcD11V69snu6=SHgLUW97tenHrcCa2w_3gmw=29Q@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \


* 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).