From: "Darrick J. Wong" <djwong@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Chandan Babu R <chandanbabu@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Re: Are jump labels broken on 6.11-rc1?
Date: Mon, 16 Sep 2024 09:08:01 -0700 [thread overview]
Message-ID: <20240916160801.GA182194@frogsfrogsfrogs> (raw)
In-Reply-To: <20240905091605.GE4928@noisy.programming.kicks-ass.net>
On Thu, Sep 05, 2024 at 11:16:05AM +0200, Peter Zijlstra wrote:
> On Thu, Sep 05, 2024 at 10:12:41AM +0200, Peter Zijlstra wrote:
> > On Mon, Aug 26, 2024 at 08:35:06PM -0700, Darrick J. Wong wrote:
>
> > > [33965.988873] ------------[ cut here ]------------
> > > [33966.013870] WARNING: CPU: 1 PID: 8992 at kernel/jump_label.c:295 __static_key_slow_dec_cpuslocked.part.0+0xb0/0xc0
>
> > > [33966.040184] pc : __static_key_slow_dec_cpuslocked.part.0+0xb0/0xc0
> > > [33966.042845] lr : __static_key_slow_dec_cpuslocked.part.0+0x48/0xc0
>
> > > [33966.072840] Call trace:
> > > [33966.073838] __static_key_slow_dec_cpuslocked.part.0+0xb0/0xc0
> > > [33966.076105] static_key_slow_dec+0x48/0x88
>
> > > This corresponds to the:
> > >
> > > WARN_ON_ONCE(!static_key_slow_try_dec(key));
> >
> > But but but,... my patch killed that function. So are you sure it is
> > applied ?!
> >
> > Because this sounds like exactly that issue again.
> >
> > Anyway, it appears I had totally forgotten about this issue again due to
> > holidays, sorry. Let me stare hard at Thomas' patch and make a 'pretty'
> > one that does boot.
>
> I've taken tglx's version with a small change (added comment) and boot
> tested it and queued it here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/urgent
>
> Could you please double check on both x86_64 and arm64?
Will send this out on the test farm tonight, thanks for the patch.
> If green by with the build robots and your own testing I'll push this
> into tip/locking/urgent to be sent to Linus on Sunday. Hopefully finally
> resolving this issue.
Sorry I didn't get to this earlier; I've been on vacation since the end
of August. Now to get to the ~1300 fsdevel emails... ;)
--D
next prev parent reply other threads:[~2024-09-16 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 3:38 Are jump labels broken on 6.11-rc1? Darrick J. Wong
2024-07-30 7:30 ` Chandan Babu R
2024-07-30 13:26 ` Peter Zijlstra
2024-07-30 13:59 ` Darrick J. Wong
2024-07-31 0:19 ` Darrick J. Wong
2024-07-31 3:10 ` Darrick J. Wong
2024-07-31 5:33 ` Darrick J. Wong
2024-07-31 10:55 ` Peter Zijlstra
2024-08-05 14:35 ` Darrick J. Wong
2024-08-06 9:44 ` Peter Zijlstra
2024-08-06 10:38 ` Peter Zijlstra
2024-08-06 22:01 ` Darrick J. Wong
2024-08-07 14:03 ` Thomas Gleixner
2024-08-07 14:34 ` Peter Zijlstra
2024-08-07 14:55 ` Thomas Gleixner
2024-08-07 15:05 ` Darrick J. Wong
2024-08-07 22:51 ` Darrick J. Wong
2024-08-27 3:35 ` Darrick J. Wong
2024-09-05 8:12 ` Peter Zijlstra
2024-09-05 9:16 ` Peter Zijlstra
2024-09-16 16:08 ` Darrick J. Wong [this message]
2024-09-19 23:41 ` Darrick J. Wong
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=20240916160801.GA182194@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).