From: Sasha Levin <sashal@kernel.org>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Patch "l2tp: Serialize access to sk_user_data with sk_callback_lock" has been added to the 6.0-stable tree
Date: Tue, 22 Nov 2022 19:37:19 -0500 [thread overview]
Message-ID: <Y31rP+RyIaye5UrC@sashalap> (raw)
In-Reply-To: <87wn7mlxxe.fsf@cloudflare.com>
On Tue, Nov 22, 2022 at 06:06:12PM +0100, Jakub Sitnicki wrote:
>Hi Sasha,
>
>On Tue, Nov 22, 2022 at 10:19 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.
>
>"Just when I thought I was out, they pull me back in!"
>
>Greg assured me yesterday that this was dropped from stable queues:
>
>https://lore.kernel.org/stable/Y3thooxAN2Are7Ai@kroah.com/
Ah yes, sorry about that, I'll throw it out.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-11-23 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221122151904.89804-1-sashal@kernel.org>
2022-11-22 17:06 ` 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-23 0:37 ` Sasha Levin [this message]
[not found] <20221121050850.2600439-1-sashal@kernel.org>
2022-11-21 9:05 ` Jakub Sitnicki
2022-11-21 11:31 ` Greg KH
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=Y31rP+RyIaye5UrC@sashalap \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=jakub@cloudflare.com \
--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