All of lore.kernel.org
 help / color / mirror / Atom feed
From: shaozhengchao <shaozhengchao@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <netdev@vger.kernel.org>,
	<davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
	<yoshfuji@linux-ipv6.org>, <kuba@kernel.org>,
	<edumazet@google.com>, <kuniyu@amazon.com>,
	<weiyongjun1@huawei.com>, <yuehaibing@huawei.com>
Subject: Re: [PATCH stable,5.10 0/2] introduce stop timer to solve the problem of CVE-2024-26865
Date: Mon, 29 Apr 2024 20:01:44 +0800	[thread overview]
Message-ID: <ee497098-6a14-f833-3c6f-a8b31259ad36@huawei.com> (raw)
In-Reply-To: <2024042934-dreadful-litigate-9064@gregkh>


Hi Greg KH:
   Thanks for the heads-up. I will work for 5.15.y and 4.19.y.

Thank you.

Zhengchao Shao

On 2024/4/29 19:11, Greg KH wrote:
> On Sun, Apr 28, 2024 at 11:49:46AM +0800, Zhengchao Shao wrote:
>> For the CVE-2024-26865 issue, the stable 5.10 branch code also involves
>> this issue. However, the patch of the mainline version cannot be used on
>> stable 5.10 branch. The commit 740ea3c4a0b2("tcp: Clean up kernel
>> listener' s reqsk in inet_twsk_purge()") is required to stop the timer.
> 
> This is also needed for 5.15.y, so we can not take a 5.10.y only patch,
> you know this :(
> 
> Please also provide a working set of 5.15.y patches and then I'll be
> glad to queue these 5.10.y ones up.
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2024-04-29 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28  3:49 [PATCH stable,5.10 0/2] introduce stop timer to solve the problem of CVE-2024-26865 Zhengchao Shao
2024-04-28  3:49 ` [PATCH stable,5.10 1/2] tcp: Clean up kernel listener's reqsk in inet_twsk_purge() Zhengchao Shao
2024-04-28  3:49 ` [PATCH stable,5.10 2/2] tcp: Fix NEW_SYN_RECV handling " Zhengchao Shao
2024-04-29 11:11 ` [PATCH stable,5.10 0/2] introduce stop timer to solve the problem of CVE-2024-26865 Greg KH
2024-04-29 12:01   ` shaozhengchao [this message]
2024-04-29 13:33     ` 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=ee497098-6a14-f833-3c6f-a8b31259ad36@huawei.com \
    --to=shaozhengchao@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=weiyongjun1@huawei.com \
    --cc=yoshfuji@linux-ipv6.org \
    --cc=yuehaibing@huawei.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.