From: Peter Zijlstra <peterz@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Filipe Manana <fdmanana@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
David Sterba <dsterba@suse.com>
Subject: Re: possible lockdep regression introduced by 4d004099a668 ("lockdep: Fix lockdep recursion")
Date: Mon, 26 Oct 2020 13:30:31 +0100 [thread overview]
Message-ID: <20201026123031.GO2594@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201026115541.GC28769@quack2.suse.cz>
On Mon, Oct 26, 2020 at 12:55:41PM +0100, Jan Kara wrote:
> > Make sure you have commit:
> >
> > f8e48a3dca06 ("lockdep: Fix preemption WARN for spurious IRQ-enable")
> >
> > (in Linus' tree by now) and do you have CONFIG_DEBUG_PREEMPT enabled?
>
> Hum, I am at 5.10-rc1 now and above mentioned commit doesn't appear to be
> there? Also googling for the title doesn't help...
*groan*... I seem to have forgotten to push it out to tip/locking/urgent on
Friday :/
Find it here:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/urgent
next prev parent reply other threads:[~2020-10-26 12:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 11:26 possible lockdep regression introduced by 4d004099a668 ("lockdep: Fix lockdep recursion") Filipe Manana
2020-10-26 11:40 ` Peter Zijlstra
2020-10-26 11:55 ` Jan Kara
2020-10-26 11:59 ` Filipe Manana
2020-10-26 12:30 ` Peter Zijlstra [this message]
2020-10-26 11:56 ` Filipe Manana
2020-10-26 12:55 ` Peter Zijlstra
2020-10-26 13:06 ` Filipe Manana
2020-10-26 15:22 ` Peter Zijlstra
2020-10-27 9:49 ` Anatoly Pugachev
2020-10-31 11:30 ` [tip: locking/urgent] locking/lockdep: Remove more raw_cpu_read() usage tip-bot2 for Peter Zijlstra
2020-11-02 17:58 ` possible lockdep regression introduced by 4d004099a668 ("lockdep: Fix lockdep recursion") Filipe Manana
2020-11-03 10:15 ` Jan Kara
2020-11-03 10:22 ` Filipe Manana
2020-10-26 20:35 ` David Sterba
2020-11-03 14:08 ` Boqun Feng
2020-11-03 14:24 ` Filipe Manana
2020-11-03 19:44 ` Filipe Manana
2020-11-04 2:22 ` Boqun Feng
2020-11-04 3:44 ` Boqun Feng
2020-11-04 9:49 ` Filipe Manana
2020-11-04 19:54 ` Filipe Manana
2020-11-05 1:10 ` Boqun Feng
2020-11-09 8:44 ` Boqun Feng
2020-11-09 9:57 ` Filipe Manana
2020-11-10 1:41 ` Boqun Feng
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=20201026123031.GO2594@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.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).