[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8b63387a09ca7b007241f328c5688c702b179019.camel@intel.com>
Date: Wed, 26 Jul 2023 18:11:52 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "mingo@...nel.org" <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "david@...hat.com" <david@...hat.com>,
"Xu, Pengfei" <pengfei.xu@...el.com>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>, "bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"keescook@...omium.org" <keescook@...omium.org>,
"john.allen@....com" <john.allen@....com>,
"rppt@...nel.org" <rppt@...nel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [tip: x86/shstk] mm: Don't allow write GUPs to shadow stack
memory
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.
Powered by blists - more mailing lists