From: Jakub Kicinski <kuba@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
stable-commits@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Patch "skbuff: don't mix ubuf_info from different sources" has been added to the 5.19-stable tree
Date: Mon, 15 Aug 2022 08:37:53 -0700 [thread overview]
Message-ID: <20220815083753.6b5da2a4@kernel.org> (raw)
In-Reply-To: <4c748c4f-e3a6-8325-fa34-ad6f056830b9@gmail.com>
On Mon, 15 Aug 2022 13:30:26 +0100 Pavel Begunkov wrote:
> On 8/13/22 21:29, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > skbuff: don't mix ubuf_info from different sources
> >
> > to the 5.19-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > skbuff-don-t-mix-ubuf_info-from-different-sources.patch
> > and it can be found in the queue-5.19 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> It doesn't hurt but we don't need it in 5.19, added only because of
> 5.20 io_uring zerocopy send work.
Concerning, I already said this doesn't need to be backported,
something's not working here, Sasha...
https://lore.kernel.org/r/20220808114451.78686a5b@kernel.org/
parent reply other threads:[~2022-08-15 15:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4c748c4f-e3a6-8325-fa34-ad6f056830b9@gmail.com>]
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=20220815083753.6b5da2a4@kernel.org \
--to=kuba@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).