From: Greg KH <gregkh@linuxfoundation.org>
To: Zhengchao Shao <shaozhengchao@huawei.com>
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: Thu, 23 May 2024 13:34:19 +0200 [thread overview]
Message-ID: <2024052355-doze-implicate-236d@gregkh> (raw)
In-Reply-To: <20240506030554.3168143-1-shaozhengchao@huawei.com>
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
next prev parent reply other threads:[~2024-05-23 11:34 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 ` Greg KH [this message]
2024-05-25 9:33 ` [PATCH stable,5.15 0/2] Revert the patchset for fix CVE-2024-26865 shaozhengchao
2024-05-25 9:42 ` Greg KH
2024-05-25 10:21 ` shaozhengchao
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=2024052355-doze-implicate-236d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=shaozhengchao@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).