From: Tong Tiangen <tongtiangen@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <peterz@infradead.org>, <keescook@chromium.org>,
<sethjenkins@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <bp@suse.de>,
<stable@vger.kernel.org>, <tongtiangen@huawei.com>
Subject: Re: Consultation on backport 97e3d26b5e5f("x86/mm: Randomize per-cpu entry area") to stable
Date: Tue, 21 Feb 2023 15:46:27 +0800 [thread overview]
Message-ID: <e2fea1a1-982d-20c8-d92c-bc4ed4d1d711@huawei.com> (raw)
In-Reply-To: <Y/RzDvXr/iGpHl+f@kroah.com>
在 2023/2/21 15:30, Greg KH 写道:
> On Tue, Feb 21, 2023 at 03:19:05PM +0800, Tong Tiangen wrote:
>> Hi peter:
>>
>> Do you have any plans to backport this patch[1] to the stable branch of the
>> lower version, such as 4.19.y ?
>
> Why? That is a new feature for 6.2 why would it be needed to fix
> anything in really old kernels?
Hi Greg:
This patch fix CVE-2023-0597[1], this CVE report a flaw possibility of
memory leak. And this is important for some products using this stable
version.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2165926
>
>> When I try to backport this patch to 5.10.y, I met some KASAN[2] and
>> KASLR[3] related issues. Although they were finally solved, there were still
>> some detours in the process.
>
> Send your series of backports to the list for review please if they
> match the stable kernel rules.
OK.
>
> But why can't you just use the 6.2 kernel instead of something obsolete
> like 4.19?
>
> thanks,
>
> greg k-h
> .
Thanks.
Tong
.
next prev parent reply other threads:[~2023-02-21 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 7:19 Consultation on backport 97e3d26b5e5f("x86/mm: Randomize per-cpu entry area") to stable Tong Tiangen
2023-02-21 7:23 ` Tong Tiangen
2023-02-21 7:30 ` Greg KH
2023-02-21 7:46 ` Tong Tiangen [this message]
2023-02-21 8:40 ` Greg KH
2023-02-21 9:19 ` Tong Tiangen
2023-02-21 10:40 ` Greg KH
2023-02-21 12:30 ` Tong Tiangen
[not found] ` <CALxfFW6zgTEj3b==g5tWXaufAaVCAe6Uh8pKda-O20OOToRAJg@mail.gmail.com>
2023-02-22 2:14 ` Tong Tiangen
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=e2fea1a1-982d-20c8-d92c-bc4ed4d1d711@huawei.com \
--to=tongtiangen@huawei.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=peterz@infradead.org \
--cc=sethjenkins@google.com \
--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