From: patchwork-bot+netdevbpf@kernel.org
To: William Tu <witu@nvidia.com>
Cc: netdev@vger.kernel.org, u9012063@gmail.com, micron10@gmail.com
Subject: Re: [PATCH net] vmxnet3: Fix missing reserved tailroom
Date: Thu, 14 Mar 2024 11:50:29 +0000 [thread overview]
Message-ID: <171041702966.3013.11175078666174379308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240309183147.28222-1-witu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 9 Mar 2024 20:31:47 +0200 you wrote:
> Use rbi->len instead of rcd->len for non-dataring packet.
>
> Found issue:
> XDP_WARN: xdp_update_frame_from_buff(line:278): Driver BUG: missing reserved tailroom
> WARNING: CPU: 0 PID: 0 at net/core/xdp.c:586 xdp_warn+0xf/0x20
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W O 6.5.1 #1
> RIP: 0010:xdp_warn+0xf/0x20
> ...
> ? xdp_warn+0xf/0x20
> xdp_do_redirect+0x15f/0x1c0
> vmxnet3_run_xdp+0x17a/0x400 [vmxnet3]
> vmxnet3_process_xdp+0xe4/0x760 [vmxnet3]
> ? vmxnet3_tq_tx_complete.isra.0+0x21e/0x2c0 [vmxnet3]
> vmxnet3_rq_rx_complete+0x7ad/0x1120 [vmxnet3]
> vmxnet3_poll_rx_only+0x2d/0xa0 [vmxnet3]
> __napi_poll+0x20/0x180
> net_rx_action+0x177/0x390
>
> [...]
Here is the summary with links:
- [net] vmxnet3: Fix missing reserved tailroom
https://git.kernel.org/netdev/net/c/e127ce7699c1
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:[~2024-03-14 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 18:31 [PATCH net] vmxnet3: Fix missing reserved tailroom William Tu
2024-03-12 10:56 ` Paolo Abeni
2024-03-12 11:39 ` Martin Zaharinov
2024-03-14 11:50 ` 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=171041702966.3013.11175078666174379308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=micron10@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.com \
--cc=witu@nvidia.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).