From: patchwork-bot+netdevbpf@kernel.org
To: Lin Ma <malin89@huawei.com>
Cc: kuba@kernel.org, avkrasnov@salutedevices.com,
cenxianlong@huawei.com, chenzhe@huawei.com,
cuirongzhen@huawei.com, davem@davemloft.net, edumazet@google.com,
eperezma@redhat.com, horms@kernel.org, jasowang@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mst@redhat.com, netdev@vger.kernel.org, pabeni@redhat.com,
sgarzare@redhat.com, stefanha@redhat.com, tanjingguo@huawei.com,
virtualization@lists.linux.dev, xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH net v2] vsock/virtio: bind uarg before filling zerocopy skb
Date: Fri, 29 May 2026 19:50:12 +0000 [thread overview]
Message-ID: <178008421264.1939215.14797550643980385939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260527023301.1075581-1-malin89@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 May 2026 10:33:01 +0800 you wrote:
> From: Jingguo Tan <tanjingguo@huawei.com>
>
> virtio_transport_send_pkt_info() allocates or reuses the zerocopy uarg
> before entering the send loop, but virtio_transport_alloc_skb() still
> fills the skb before it inherits that uarg. When fixed-buffer vectored
> zerocopy hits MAX_SKB_FRAGS, io_sg_from_iter() may partially attach
> managed frags and return -EMSGSIZE. The rollback path call kfree_skb()
> to free an skb that carries SKBFL_MANAGED_FRAG_REFS but no uarg, so
> skb_release_data() falls through to ordinary frag unref.
>
> [...]
Here is the summary with links:
- [net,v2] vsock/virtio: bind uarg before filling zerocopy skb
https://git.kernel.org/netdev/net/c/1e584c304cfb
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-05-29 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 2:33 [PATCH net v2] vsock/virtio: bind uarg before filling zerocopy skb Lin Ma
2026-05-29 19: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=178008421264.1939215.14797550643980385939.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=cenxianlong@huawei.com \
--cc=chenzhe@huawei.com \
--cc=cuirongzhen@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malin89@huawei.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=tanjingguo@huawei.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox