All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
	xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	sdf@fomichev.me, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] virtio-net: xsk: rx: fix the frame's length check
Date: Thu, 03 Jul 2025 09:40:08 +0000	[thread overview]
Message-ID: <175153560802.1029220.2379425113852015641.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250630151315.86722-1-minhquangbui99@gmail.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 30 Jun 2025 22:13:13 +0700 you wrote:
> Hi everyone,
> 
> This series contains 2 patches for the zerocopy XDP receive path in virtio
> net
> - Patch 1: there is a difference between first buffer and the following
> buffers in this receive path. While the first buffer contains virtio
> header, the following ones do not. So the length of the remaining region
> for frame data is also different in 2 cases. The current maximum frame's
> length check is only correct for the following buffers not the first one.
> - Patch 2: no functional change. The tricky xdp->data adjustment due to
> the above difference is moved to buf_to_xdp() so that this helper contains
> all logic to build xdp_buff and the tricky adjustment does not scatter
> over different functions.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/2] virtio-net: xsk: rx: fix the frame's length check
    https://git.kernel.org/netdev/net/c/5177373c3131
  - [net,v3,2/2] virtio-net: xsk: rx: move the xdp->data adjustment to buf_to_xdp()
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-07-03  9:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 15:13 [PATCH net v3 0/2] virtio-net: xsk: rx: fix the frame's length check Bui Quang Minh
2025-06-30 15:13 ` [PATCH net v3 1/2] " Bui Quang Minh
2025-06-30 15:13 ` [PATCH net v3 2/2] virtio-net: xsk: rx: move the xdp->data adjustment to buf_to_xdp() Bui Quang Minh
2025-07-01  2:23   ` Jason Wang
2025-07-03  9:25     ` Paolo Abeni
2025-07-03  9:40 ` patchwork-bot+netdevbpf [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=175153560802.1029220.2379425113852015641.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minhquangbui99@gmail.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.