From: sashiko-bot@kernel.org
To: "Mina Almasry" <almasrymina@google.com>,
virtualization@lists.linux.dev, linux-rdma@vger.kernel.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net-next v1 1/5] net: skbuff: skip managed zerocopy frags in skb_frag_ref()
Date: Wed, 04 Nov 2026 21:14:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-198070@kernel.org> (raw)
In-Reply-To: <20261103211424.127627-2-almasrymina@google.com>
> skb_frag_unref() and skb_release_data() skip releasing references on
> managed zerocopy fragments (SKBFL_MANAGED_FRAG_REFS), whereas
> skb_frag_ref() acquires a reference unconditionally. If skb_frag_ref()
> is called on a managed zerocopy SKB, the acquired reference is never
> released by skb_frag_unref() or skb_release_data().
>
> Skip acquiring a reference in skb_frag_ref() when skb_zcopy_managed(skb)
> is true so skb_frag_ref() matches skb_frag_unref() and
> skb_release_data(), and disable share_ok in iptfs_output_queued() when
> skb_zcopy_managed(skb) is true so iptfs_consume_frags() does not append
> unreferenced fragments into a managed zerocopy outer SKB.
>
> Signed-off-by: Mina Almasry <almasrymina@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103211424.127627-1-almasrymina@google.com?part=1
next prev parent reply other threads:[~2026-11-04 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 21:14 [PATCH net-next v1 0/5] net: deprecate skb->pp_recycle and skb_mark_for_recycle() Mina Almasry
2026-11-03 21:14 ` [PATCH net-next v1 1/5] net: skbuff: skip managed zerocopy frags in skb_frag_ref() Mina Almasry
2026-11-04 21:14 ` sashiko-bot [this message]
2026-11-03 21:14 ` [PATCH net-next v1 2/5] net: skbuff: refcount spliced page_pool frags via skb_pipe_buf_ops Mina Almasry
2026-11-04 21:14 ` sashiko-bot
2026-11-03 21:14 ` [PATCH net-next v1 3/5] net: datagram: refcount page_pool frags in zerocopy_fill_skb_from_iter() Mina Almasry
2026-11-04 21:14 ` sashiko-bot
2026-11-05 12:45 ` Loktionov, Aleksandr
2026-11-03 21:14 ` [PATCH net-next v1 4/5] net: remove skb->pp_recycle and consolidate netmem refcounting Mina Almasry
2026-11-04 21:14 ` sashiko-bot
2026-11-06 19:36 ` Mina Almasry
2026-11-03 21:14 ` [PATCH net-next v1 5/5] net: remove skb_mark_for_recycle() Mina Almasry
2026-11-04 21:14 ` sashiko-bot
2026-11-05 16:35 ` [PATCH net-next v1 0/5] net: deprecate skb->pp_recycle and skb_mark_for_recycle() Jesper Dangaard Brouer
2026-11-06 17:53 ` Mina Almasry
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=sashiko-outbox-198070@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=almasrymina@google.com \
--cc=eperezma@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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.