Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Tong Tiangen <tongtiangen@huawei.com>
To: <peterz@infradead.org>
Cc: <keescook@chromium.org>, <sethjenkins@google.com>,
	Dave Hansen <dave.hansen@linux.intel.com>, <bp@suse.de>,
	<stable@vger.kernel.org>
Subject: Consultation on backport 97e3d26b5e5f("x86/mm: Randomize per-cpu entry area") to stable
Date: Tue, 21 Feb 2023 15:19:05 +0800	[thread overview]
Message-ID: <2b814e48-d304-e48a-e4b4-c39a10d2dbf4@huawei.com> (raw)

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 ?
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.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97e3d26b5e5f371b3ee223d94dd123e6c442ba80
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3f148f3318140035e87decc1214795ff0755757b
[3]

Best Regards,
Tong

.

             reply	other threads:[~2023-02-21  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  7:19 Tong Tiangen [this message]
2023-02-21  7:23 ` Consultation on backport 97e3d26b5e5f("x86/mm: Randomize per-cpu entry area") to stable Tong Tiangen
2023-02-21  7:30 ` Greg KH
2023-02-21  7:46   ` Tong Tiangen
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=2b814e48-d304-e48a-e4b4-c39a10d2dbf4@huawei.com \
    --to=tongtiangen@huawei.com \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --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