From: Sasha Levin <sashal@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Minh Nguyen <minhnguyen.080505@gmail.com>,
Willem de Bruijn <willemb@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Please apply 98d0912e9f84 ("net: skbuff: fix missing zerocopy reference in pskb_carve helpers") to 6.1.y
Date: Thu, 11 Jun 2026 11:26:23 -0400 [thread overview]
Message-ID: <20260611-stable-reply-0105@kernel.org> (raw)
In-Reply-To: <aioyuCnSKlch1wdv@eldamar.lan>
On Thu, Jun 11, 2026 at 05:59:52AM +0200, Salvatore Bonaccorso wrote:
> I tested down to 6.1.y; the 6.6.y commit needs to be slightly
> different. I have not tested 5.15/5.10 (no net_zcopy_get() in 5.10.y,
> so more work there). Should I send an explicit 6.6.y patch, or will
> you pick the change for 6.6.y and 6.1.y yourself?
Your 6.1.y patch applies cleanly and looks correct. But I can't queue it
on its own: 98d0912e9f84 isn't in 6.6.y yet, and I don't add a fix to an
older tree while a newer one is missing it. So I'm holding the 6.1.y
change until 6.6.y is sorted.
Rather than have me hand-adapt the other trees, please send explicit
per-branch backports: your 6.1 patch doesn't apply cleanly to 6.6.y
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-06-11 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 19:16 Please apply 98d0912e9f84 ("net: skbuff: fix missing zerocopy reference in pskb_carve helpers") to 6.1.y Salvatore Bonaccorso
2026-06-11 0:45 ` Sasha Levin
2026-06-11 3:59 ` Salvatore Bonaccorso
2026-06-11 15:26 ` Sasha Levin [this message]
2026-06-11 16:29 ` Please apply 98d0912e9f84 ("net: skbuff: fix missing zerocopy reference in pskb_carve helpers") down " Salvatore Bonaccorso
2026-06-12 14:41 ` Sasha Levin
2026-06-13 0:20 ` Sasha Levin
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=20260611-stable-reply-0105@kernel.org \
--to=sashal@kernel.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=minhnguyen.080505@gmail.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.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 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.