From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "david@redhat.com" <david@redhat.com>,
"Xu, Pengfei" <pengfei.xu@intel.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"john.allen@amd.com" <john.allen@amd.com>,
"rppt@kernel.org" <rppt@kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [tip: x86/shstk] mm: Don't allow write GUPs to shadow stack memory
Date: Wed, 26 Jul 2023 18:11:52 +0000 [thread overview]
Message-ID: <8b63387a09ca7b007241f328c5688c702b179019.camel@intel.com> (raw)
In-Reply-To: <1b5d436e1b4f31c37ce1f1e6342c836fd5b2ceec.camel@intel.com>
On Fri, 2023-07-21 at 09:24 -0700, Rick Edgecombe wrote:
> As for the build breakage, I'm not sure how this slipped through. My
> runtime test environment was missing CONFIG_WERROR, but I got 0day
> build successes for the x86_64 and i386 defconfigs specifically. I'll
> have to follow up with the 0day people.
Yea, there was a 0-day bug that caused it to ignore Wunused-function
warnings. Apparently 0-day also forces CONFIG_WERROR=n, so the build
erroneously succeeded.
The Wunused-function bug is fixed now on 0-day, and the fixed shadow
stack branch re-tested by it. Dave had pushed the shadow stack fix to
his repo as well, so I'm assuming he will handle getting the fix into
tip. But please let me know if you need anything from me, and sorry for
the hassle.
next prev parent reply other threads:[~2023-07-26 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 22:47 tip-bot2 for Rick Edgecombe
2023-07-21 8:34 ` Ingo Molnar
2023-07-21 16:24 ` Edgecombe, Rick P
2023-07-26 18:11 ` Edgecombe, Rick P [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 22:19 tip-bot2 for Rick Edgecombe
2023-06-16 19:16 tip-bot2 for Rick Edgecombe
2023-03-20 16:39 tip-bot2 for Rick Edgecombe
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=8b63387a09ca7b007241f328c5688c702b179019.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=john.allen@amd.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pengfei.xu@intel.com \
--cc=rppt@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
all inboxes | Powered by JetHome®