From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: 592dc8b215 ("lockdep: Prepare for NMI IRQ state tracking"): [ 5.103068] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3765 lockdep_hardirqs_off
Date: Tue, 02 Jun 2020 12:21:56 +0200 [thread overview]
Message-ID: <20200602102156.GS706495@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200602002815.GD12456@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
On Tue, Jun 02, 2020 at 08:28:16AM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://github.com/0day-ci/linux/commits/Peter-Zijlstra/x86-entry-lockdep-Improve-IRQ-state-tracking/20200528-222257
I did ask you to stop scraping my patches from lkml. I'll stick them in
a git tree (they _are_ in a git tree), build those.
That said; yes, this patch is buggered, Rostedt already noted that on
review Friday.
next prev parent reply other threads:[~2020-06-02 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 0:28 592dc8b215 ("lockdep: Prepare for NMI IRQ state tracking"): [ 5.103068] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3765 lockdep_hardirqs_off kernel test robot
2020-06-02 10:21 ` Peter Zijlstra [this message]
2020-06-02 11:51 ` Philip Li
2020-06-02 12:33 ` Peter Zijlstra
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=20200602102156.GS706495@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.