From: patchwork-bot+netdevbpf@kernel•org
To: Nikolay Aleksandrov <razor@blackwall•org>
Cc: netdev@vger•kernel.org, kuba@kernel•org, davem@davemloft•net,
stable@vger•kernel.org, jasowang@redhat•com,
xuanzhuo@linux•alibaba.com, daniel@iogearbox•net, mst@redhat•com,
virtualization@lists•linux-foundation.org
Subject: Re: [PATCH net v3] virtio_net: fix wrong buf address calculation when using xdp
Date: Tue, 26 Apr 2022 13:00:10 +0000 [thread overview]
Message-ID: <165097801081.17994.867649031795224132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220425103703.3067292-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat•com>:
On Mon, 25 Apr 2022 13:37:03 +0300 you wrote:
> We received a report[1] of kernel crashes when Cilium is used in XDP
> mode with virtio_net after updating to newer kernels. After
> investigating the reason it turned out that when using mergeable bufs
> with an XDP program which adjusts xdp.data or xdp.data_meta page_to_buf()
> calculates the build_skb address wrong because the offset can become less
> than the headroom so it gets the address of the previous page (-X bytes
> depending on how lower offset is):
> page_to_skb: page addr ffff9eb2923e2000 buf ffff9eb2923e1ffc offset 252 headroom 256
>
> [...]
Here is the summary with links:
- [net,v3] virtio_net: fix wrong buf address calculation when using xdp
https://git.kernel.org/netdev/net/c/acb16b395c3f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-26 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 10:37 [PATCH net v3] virtio_net: fix wrong buf address calculation when using xdp Nikolay Aleksandrov
2022-04-25 11:37 ` Xuan Zhuo
2022-04-25 13:10 ` Daniel Borkmann
2022-04-25 13:52 ` Michael S. Tsirkin
2022-04-26 2:22 ` Jason Wang
2022-04-26 13:00 ` 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=165097801081.17994.867649031795224132.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=jasowang@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=razor@blackwall$(echo .)org \
--cc=stable@vger$(echo .)kernel.org \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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