Re: Crash on boot with CONFIG_JUMP_LABEL in 6.10

[matoro <matoro_mailinglist_kernel@matoro.tk>]

On 2024-07-31 13:00, Sam James wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
> 
>> On Wed, Jul 31, 2024 at 02:31:55PM +0100, Sam James wrote:
>>> Peter Zijlstra <peterz@infradead.org> writes:
>>> 
>>> > On Tue, Jul 30, 2024 at 08:36:13PM -0400, matoro wrote:
>>> >> On 2024-07-30 09:50, John David Anglin wrote:
>>> >> > On 2024-07-30 9:41 a.m., John David Anglin wrote:
>>> >> > > On 2024-07-29 7:11 p.m., matoro wrote:
>>> >> > > > Hi all, just bumped to the newest mainline starting with 6.10.2
>>> >> > > > and immediately ran into a crash on boot. Fully reproducible,
>>> >> > > > reverting back to last known good (6.9.8) resolves the issue. 
>>> >> > > > Any clue what's going on here?
>>> >> > > > I can provide full boot logs, start bisecting, etc if needed...
>>> >> > > 6.10.2 built and booted okay on my c8000 with the attached config.
>>> >> > > You could start
>>> >> > > with it and incrementally add features to try to identify the one
>>> >> > > that causes boot failure.
>>> >> > Oh, I have an experimental clocksource patch installed.  You will need
>>> >> > to regenerate config
>>> >> > with "make oldconfig" to use the current timer code.  Probably, this
>>> >> > would happen automatically.
>>> >> > >
>>> >> > > Your config would be needed to duplicate.    Full boot log would also help.
>>> >> >
>>> >> > Dave
>>> >>
>>> >> Hi Dave, bisecting quickly revealed the cause here.
>>> >
>>> > https://lkml.kernel.org/r/20240731105557.GY33588@noisy.programming.kicks-ass.net
>>> 
>>> Greg, I see tglx's jump_label fix is queued for 6.10.3 but this one
>>> isn't as it came too late. Is there any chance of chucking it in? It's
>>> pretty nasty.
>> 
>> What is the git id of this in Linus's tree?
> 
> Ah, you're right, it's not there. Sorry, I thought I'd seen it pulled.
> 
>> 
>> thanks,
>> 
>> greg k-h

Hi Peter, sorry I'm not quite following, exactly what patches need to be 
applied to fix this?  I checked out the thread you linked but it does not 
apply cleanly to 6.10.