BPF List
 help / color / mirror / Atom feed
From: Lina Wang <lina.wang@mediatek.com>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	<linux-kernel@vger.kernel.org>,
	Maciej enczykowski <maze@google.com>, <netdev@vger.kernel.org>,
	<linux-kselftest@vger.kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH v3] net: fix wrong network header length
Date: Thu, 7 Apr 2022 17:38:43 +0800	[thread overview]
Message-ID: <20220407093843.10538-1-lina.wang@mediatek.com> (raw)
In-Reply-To: <CAADnVQJEXOOH6--uA7BvFUPmXY42zeOQVweHmaMqkbj_g5TLqA@mail.gmail.com>

On Thu, Feb 17, 2022 at 12:45 AM Paolo Abeni <pabeni@redhat.com> wrote:
>
> Hello,
>
> On Thu, 2022-02-17 at 15:01 +0800, Lina Wang wrote:

> So that bpf helper has to be somehow involved, but iperf udp test
> says nothing about it.
> Please craft a _complete_ selftest.

Finally, I have wrote selftest, please check 
https://lore.kernel.org/bpf/20220407084727.10241-1-lina.wang@mediatek.com/
https://lore.kernel.org/bpf/20220407084727.10241-2-lina.wang@mediatek.com/
https://lore.kernel.org/bpf/20220407084727.10241-3-lina.wang@mediatek.com/ 

Thanks

      parent reply	other threads:[~2022-04-07  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  7:30 [PATCH v3] net: fix wrong network header length Lina Wang
2022-02-17  3:05 ` Alexei Starovoitov
2022-02-17  7:01   ` Lina Wang
2022-02-17  8:45     ` Paolo Abeni
2022-02-17 17:05       ` Alexei Starovoitov
2022-02-18  2:23         ` Lina Wang
2022-04-07  9:38         ` Lina Wang [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=20220407093843.10538-1-lina.wang@mediatek.com \
    --to=lina.wang@mediatek.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@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