From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next] eth: fbnic: put back netmem reference xdp_buff_add_frag() fails
Date: Thu, 24 Sep 2026 11:10:08 +0000 [thread overview]
Message-ID: <179024820851.1482887.2143457542729538087.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922-fbnic-refcount-fix-v1-1-31e5862c9893@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 22 Sep 2026 12:53:28 -0700 you wrote:
> fbnic_add_rx_frag() takes a page_pool reference out of the buffer's
> pagecnt_bias before handing the fragment to xdp_buff_add_frag(). If that
> call fails it has not taken ownership of the netmem: the fragment is not
> recorded in the shared info, and fbnic_put_pkt_buff() will not put the
> reference back.
>
> Put the netmem reference back on the failure path.
>
> [...]
Here is the summary with links:
- [net-next] eth: fbnic: put back netmem reference xdp_buff_add_frag() fails
https://git.kernel.org/netdev/net-next/c/1c85ea5df86b
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:[~2026-09-24 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:53 [PATCH net-next] eth: fbnic: put back netmem reference xdp_buff_add_frag() fails Daniel Zahka
2026-09-24 11:10 ` 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=179024820851.1482887.2143457542729538087.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel.zahka@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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.