[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e5df172c76dd4bb4aeb45e4baef0eff3@AcuMS.aculab.com>
Date: Tue, 17 Mar 2020 16:35:42 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Borislav Petkov' <bp@...en8.de>, Jakub Jelinek <jakub@...hat.com>
CC: Peter Zijlstra <peterz@...radead.org>,
Sergei Trofimovich <slyfox@...too.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Ingo Molnar" <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...nel.org>,
"x86@...nel.org" <x86@...nel.org>, Michael Matz <matz@...e.de>
Subject: RE: [PATCH] x86: fix early boot crash on gcc-10
From: Borislav Petkov
> Sent: 17 March 2020 14:50
> On Tue, Mar 17, 2020 at 03:39:14PM +0100, Jakub Jelinek wrote:
> > That is because the option is called -fno-stack-protector, so one needs to
> > use __attribute__((optimize("no-stack-protector")))
>
> Ha, that works even! :-)
>
> And my guest boots.
>
> I guess we can do that then. Looks like the optimal solution to me.
>
> Also, I'm assuming older gccs will simply ignore unknown optimize
> options?
Unlikely since it rejected the misspelt one.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists