From: Steffen Klassert <steffen.klassert@secunet.com>
To: Maher Azzouzi <maherazz04@gmail.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <w@1wt.eu>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] esp: do not unref managed frag pages in esp_ssg_unref()
Date: Wed, 15 Jul 2026 12:13:54 +0200 [thread overview]
Message-ID: <alddYsnyQXXU2E1I@secunet.com> (raw)
In-Reply-To: <20260712170530.9807-1-maherazz04@gmail.com>
On Sun, Jul 12, 2026 at 06:05:30PM +0100, Maher Azzouzi wrote:
> esp_ssg_unref() releases the page references held on the source
> scatterlist after the AEAD operation completes. It calls
> skb_page_unref() on every frag page for an out-of-place transform
> (req->src != req->dst), and in the error path of esp_output_tail()
> (already_unref == true) on the request's own scatterlist.
>
> This is wrong when the skb carries managed frags
> (SKBFL_MANAGED_FRAG_REFS). Managed frags are owned by a zerocopy ubuf
> and the skb does not hold a per-frag page reference; io_uring SEND_ZC
> with a registered buffer attaches the bvec pages this way via
> io_sg_from_iter(). The rest of the stack honours this invariant:
> skb_release_data() skips the per-frag unref when SKBFL_MANAGED_FRAG_REFS
> is set, and skb_zcopy_managed() is the guard used at the other unref
> sites.
>
> esp_ssg_unref() is missing that guard, so for a managed-frag skb it
> drops a page reference the skb never acquired. This can underflow the
> page reference count and free a page that is still in use.
>
> Guard the function with skb_zcopy_managed() so both unref paths are
> skipped for managed-frag skbs, matching skb_release_data().
>
> Fixes: cac2661c53f3 ("esp4: Avoid skb_cow_data whenever possible")
> Fixes: 03e2a30f6a27 ("esp6: Avoid skb_cow_data whenever possible")
> Signed-off-by: Maher Azzouzi <maherazz04@gmail.com>
Applied to the ipsec tree, thanks a lot!
prev parent reply other threads:[~2026-07-15 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 17:05 [PATCH net] esp: do not unref managed frag pages in esp_ssg_unref() Maher Azzouzi
2026-07-15 10:13 ` Steffen Klassert [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=alddYsnyQXXU2E1I@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maherazz04@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=w@1wt.eu \
/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