[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9940d719-ee96-341d-93e6-ffd04b6fddba@huawei.com>
Date: Sat, 25 May 2024 18:21:08 +0800
From: shaozhengchao <shaozhengchao@...wei.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: <stable@...r.kernel.org>, <netdev@...r.kernel.org>, <davem@...emloft.net>,
<kuznet@....inr.ac.ru>, <yoshfuji@...ux-ipv6.org>, <kuba@...nel.org>,
<edumazet@...gle.com>, <kuniyu@...zon.com>, <weiyongjun1@...wei.com>,
<yuehaibing@...wei.com>
Subject: Re: [PATCH stable,5.15 0/2] Revert the patchset for fix
CVE-2024-26865
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
Powered by blists - more mailing lists