From: Greg KH <greg@kroah.com>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: Patch "l2tp: Serialize access to sk_user_data with sk_callback_lock" has been added to the 6.0-stable tree
Date: Mon, 21 Nov 2022 12:31:46 +0100 [thread overview]
Message-ID: <Y3thooxAN2Are7Ai@kroah.com> (raw)
In-Reply-To: <87o7t07k4l.fsf@cloudflare.com>
On Mon, Nov 21, 2022 at 10:05:11AM +0100, Jakub Sitnicki wrote:
>
> On Mon, Nov 21, 2022 at 12:08 AM -05, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > l2tp: Serialize access to sk_user_data with sk_callback_lock
> >
> > to the 6.0-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:
> > l2tp-serialize-access-to-sk_user_data-with-sk_callba.patch
> > and it can be found in the queue-6.0 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.
>
> Please don't add the commit below to stable tree, yet.
> We have a fix-up for it under review:
>
> https://lore.kernel.org/netdev/20221121085426.21315-1-jakub@cloudflare.com/
Ok, now dropped from both queues, thanks.
greg k-h
next prev parent reply other threads:[~2022-11-21 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221121050850.2600439-1-sashal@kernel.org>
2022-11-21 9:05 ` Patch "l2tp: Serialize access to sk_user_data with sk_callback_lock" has been added to the 6.0-stable tree Jakub Sitnicki
2022-11-21 11:31 ` Greg KH [this message]
[not found] <20221122151904.89804-1-sashal@kernel.org>
2022-11-22 17:06 ` Jakub Sitnicki
2022-11-23 0:37 ` 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=Y3thooxAN2Are7Ai@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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