From: Daniel Borkmann <daniel@iogearbox.net>
To: Shmulik Ladkani <shmulik@metanetworks.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [PATCH bpf-next 0/2] test_bpf: Add an skb_segment test for a linear head_frag=0 skb whose gso_size was mangled
Date: Wed, 30 Oct 2019 16:56:46 +0100 [thread overview]
Message-ID: <20191030155646.GC5669@pc-66.home> (raw)
In-Reply-To: <20191025134223.2761-1-shmulik.ladkani@gmail.com>
On Fri, Oct 25, 2019 at 04:42:21PM +0300, Shmulik Ladkani wrote:
> Add a reproducer test that mimics the input skbs that lead to the BUG_ON
> in skb_segment() which was fixed by commit 3dcbdb134f32 ("net: gso: Fix skb_segment splat when splitting gso_size mangled skb having linear-headed frag_list").
>
> Shmulik Ladkani (2):
> test_bpf: Refactor test_skb_segment() to allow testing skb_segment()
> on numerous different skbs
> test_bpf: Introduce 'gso_linear_no_head_frag' skb_segment test
>
> lib/test_bpf.c | 112 +++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 103 insertions(+), 9 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2019-10-30 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 13:42 [PATCH bpf-next 0/2] test_bpf: Add an skb_segment test for a linear head_frag=0 skb whose gso_size was mangled Shmulik Ladkani
2019-10-25 13:42 ` [PATCH bpf-next 1/2] test_bpf: Refactor test_skb_segment() to allow testing skb_segment() on numerous different skbs Shmulik Ladkani
2019-10-25 13:42 ` [PATCH bpf-next 2/2] test_bpf: Introduce 'gso_linear_no_head_frag' skb_segment test Shmulik Ladkani
2019-10-30 15:56 ` Daniel Borkmann [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=20191030155646.GC5669@pc-66.home \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@gmail.com \
--cc=shmulik@metanetworks.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).