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.15 0/2] Revert the patchset for fix CVE-2024-26865
Date: Sat, 25 May 2024 18:21:08 +0800 [thread overview]
Message-ID: <9940d719-ee96-341d-93e6-ffd04b6fddba@huawei.com> (raw)
In-Reply-To: <2024052511-aflutter-outsider-4917@gregkh>
On 2024/5/25 17:42, Greg KH wrote:
> On Sat, May 25, 2024 at 05:33:00PM +0800, shaozhengchao wrote:
>>
>>
>> On 2024/5/23 19:34, Greg KH wrote:
>>> On Mon, May 06, 2024 at 11:05:52AM +0800, Zhengchao Shao wrote:
>>>> There's no "pernet" variable in the struct hashinfo. The "pernet" variable
>>>> is introduced from v6.1-rc1. Revert pre-patch and post-patch.
>>>
>>> I do not understand, why are these reverts needed?
>>>
>>> How does the code currently build if there is no variable here?
>>>
>>> confused,
>>>
>>> greg k-h
>> Hi greg:
>> If only the first patch is merged, compilation will fail.
>> There's no "pernet" variable in the struct hashinfo.
>
> But both patches are merged together here. Does the released kernel
> versions fail to build somehow?
>
> thanks,
>
> greg k-h
>
Work well, as I know.
Thank you
Zhengchao Shao
next prev parent reply other threads:[~2024-05-25 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 3:05 [PATCH stable,5.15 0/2] Revert the patchset for fix CVE-2024-26865 Zhengchao Shao
2024-05-06 3:05 ` [PATCH stable,5.15 1/2] Revert "tcp: Fix NEW_SYN_RECV handling in inet_twsk_purge()" Zhengchao Shao
2024-05-06 3:05 ` [PATCH stable,5.15 2/2] Revert "tcp: Clean up kernel listener's reqsk " Zhengchao Shao
2024-05-23 11:34 ` [PATCH stable,5.15 0/2] Revert the patchset for fix CVE-2024-26865 Greg KH
2024-05-25 9:33 ` shaozhengchao
2024-05-25 9:42 ` Greg KH
2024-05-25 10:21 ` shaozhengchao [this message]
2024-05-25 10:42 ` Greg KH
2024-05-29 7:59 ` shaozhengchao
2024-05-29 10:02 ` Greg KH
2024-05-23 11:39 ` 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=9940d719-ee96-341d-93e6-ffd04b6fddba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox