From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86/mm for 6.2
Date: Fri, 16 Dec 2022 13:09:53 -0700 [thread overview]
Message-ID: <Y5zQkbRm9LhUSsDK@zx2c4.com> (raw)
In-Reply-To: <20221213174234.688534-1-dave.hansen@linux.intel.com>
Hi Dave,
On Tue, Dec 13, 2022 at 09:42:34AM -0800, Dave Hansen wrote:
> This includes some new randomization of the per-cpu entry areas from
> Peter Z. Without it, these areas are a tasty target for attackers.
> The entry code and mappings are especially tricky code and this has
> caused some issues along the way, but they have settled down.
> x86/mm: Randomize per-cpu entry area
I've got a trivial patch teed up for late in the window that I wanted to
send in after Linus merges this pull. I was wondering whether you were
going to send in another x86/mm pull during the merge window (perhaps
without LAM in it?), or if this whole thing is going to wait for 6.3.
Either way is fine with me, but it'd save me a lot of F5 refreshing if I
knew what to expect.
Jason
prev parent reply other threads:[~2022-12-16 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 17:42 [GIT PULL] x86/mm for 6.2 Dave Hansen
2022-12-14 22:36 ` Linus Torvalds
2022-12-15 12:30 ` kirill.shutemov
2022-12-15 17:17 ` Linus Torvalds
2022-12-15 17:26 ` Linus Torvalds
2022-12-15 21:53 ` Dave Hansen
2022-12-15 22:46 ` Linus Torvalds
2022-12-16 2:16 ` kirill.shutemov
2022-12-16 15:05 ` Kirill A. Shutemov
2022-12-16 15:43 ` Linus Torvalds
2022-12-17 16:43 ` Kirill A. Shutemov
2022-12-16 20:09 ` Jason A. Donenfeld [this message]
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=Y5zQkbRm9LhUSsDK@zx2c4.com \
--to=jason@zx2c4.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@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