[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aef4052eb8c87860d71a2648fbfb1dbd894c1531.camel@intel.com>
Date: Thu, 7 Apr 2022 15:20:48 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "peterz@...radead.org" <peterz@...radead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Poimboe, Josh" <jpoimboe@...hat.com>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: IBT related objtool warnings
On Thu, 2022-04-07 at 08:49 +0200, Peter Zijlstra wrote:
> On Wed, Apr 06, 2022 at 10:43:33PM +0000, Edgecombe, Rick P wrote:
> > Hi,
> >
> > After commit:
> > ed53a0d97192 x86/alternative: Use .ibt_endbr_seal to seal indirect
> > calls
> >
> > I am getting objtool "unreachable instruction" warnings.
> >
> > On one system with gcc 8.4.0:
> > vmlinux.o: warning: objtool: start_secondary()+0x10e: unreachable
> > instruction
> >
> > On another with gcc 11.2.1:
> > vmlinux.o: warning: objtool: pvh_start_xen()+0x0: unreachable
> > instruction
>
> Could you try with tip/x86/urgent ?
I get:
vmlinux.o: warning: objtool: start_secondary()+0x10d: unreachable
instruction
Powered by blists - more mailing lists