linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Xu <jeffxu@chromium.org>
To: linux-mm@kvack.org, "Stephen Röttger" <sroettger@chromium.org>,
	"dave.hansen@intel.com" <dave.hansen@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"Jorge Lucangeli Obes" <jorgelo@chromium.org>,
	"Kees Cook" <keescook@chromium.org>
Subject: x86/pkeys in early kernel version
Date: Wed, 25 Jan 2023 11:02:28 -0800	[thread overview]
Message-ID: <CABi2SkUycD_sHzuFNL1iCsTwH3YinhYzv18yvs+8jQyqZV9DCg@mail.gmail.com> (raw)

Hello,

I'm investigating if there is a need to backport x86/pkeys fix/feature
into earlier kernel
versions, Chrome is starting to use PKEY in x86, and I hope experts
here can give
advice on this.

For background, ChromeOS regularly syncs with upstream kernel
versions, and has production
that uses 4.4/4.14/4.19/5.4/5.10/5.15.

We plan to use PKEY as Stephen Röttger proposed in
https://docs.google.com/document/d/1O2jwK4dxI3nRcOJuPYkonhTkNQfbmwdvxQMyXgeaRHo/edit?usp=sharing
In short, Chrome will use PKEY to protect a thread and have exclusive
access to some pages.
If there are fixes/features to make this happen, we can backport those
from the ChromeOS branch.

Thanks!
Best regards,
Jeff


             reply	other threads:[~2023-01-25 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 19:02 Jeff Xu [this message]
2023-01-25 19:12 ` Dave Hansen
2023-01-26  1:43   ` Jeff Xu
2023-01-27  5:36     ` Jeff Xu
2023-01-27  5:55       ` Kyle Huey
2023-01-27 19:08         ` Jeff Xu
2023-01-27 19:22           ` Kyle Huey
2023-01-27 19:30             ` Kyle Huey
2023-01-27 21:12               ` Jeff Xu
2023-03-13 23:24                 ` Jeff Xu
2023-03-14  0:24                   ` Dave Hansen
2023-01-27 15:22     ` Dave Hansen
2023-01-27 17:58       ` Jeff Xu

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=CABi2SkUycD_sHzuFNL1iCsTwH3YinhYzv18yvs+8jQyqZV9DCg@mail.gmail.com \
    --to=jeffxu@chromium.org \
    --cc=dave.hansen@intel.com \
    --cc=jorgelo@chromium.org \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=sroettger@chromium.org \
    --cc=tglx@linutronix.de \
    /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