From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86/shstk for 6.6-rc1
Date: Thu, 31 Aug 2023 12:40:42 -0700 [thread overview]
Message-ID: <CAHk-=wipDVFEfSJxbnUSDqENs5i8RzSsgJOFdb69pH=b7BOFiQ@mail.gmail.com> (raw)
In-Reply-To: <20230830234752.19858-1-dave.hansen@linux.intel.com>
On Wed, 30 Aug 2023 at 16:48, Dave Hansen <dave.hansen@linux.intel.com> wrote:
>
> Add x86 shadow stack support
I assume you are aware of the system call renumbering from linux-next,
but I thought I'd mention it anyway. 452 was taken by fchmodat2, so
your new map_shadow_stack() system call is merged as 453.
I do also note that it looks like the merge resolution of the
_COMMON_PAGE_CHG_MASK bits in linux-next is wrong, and lost the
_PAGE_DIRTY_BITS part in Ingo's -tip merge 783560d95e0e ("Merge branch
'x86/mm' into x86/merge, to ease integration testing").
Anyway, please do double-check my merge for correctness, and test it
on some machine that hopefully supports this and has the
infrastructure set up for it.
Linus
next prev parent reply other threads:[~2023-08-31 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 23:47 [GIT PULL] x86/shstk for 6.6-rc1 Dave Hansen
2023-08-31 19:40 ` Linus Torvalds [this message]
2023-08-31 21:27 ` [PATCH] powerpc: Fix pud_mkwrite() definition after pte_mkwrite() API changes [was: Re: [GIT PULL] x86/shstk for 6.6-rc1] Ingo Molnar
2023-08-31 21:36 ` [tip: x86/merge] powerpc: Fix pud_mkwrite() definition after pte_mkwrite() API changes tip-bot2 for Ingo Molnar
2023-08-31 21:50 ` [PATCH] powerpc: Fix pud_mkwrite() definition after pte_mkwrite() API changes [was: Re: [GIT PULL] x86/shstk for 6.6-rc1] Linus Torvalds
2023-08-31 19:42 ` [GIT PULL] x86/shstk for 6.6-rc1 pr-tracker-bot
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='CAHk-=wipDVFEfSJxbnUSDqENs5i8RzSsgJOFdb69pH=b7BOFiQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).