All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
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 19:51:30 +0800	[thread overview]
Message-ID: <20200602115130.GA10863@intel.com> (raw)
In-Reply-To: <20200602102156.GS706495@hirez.programming.kicks-ass.net>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

On Tue, Jun 02, 2020 at 12:21:56PM +0200, Peter Zijlstra wrote:
> 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.
sorry for this, the mail from you is disabled per early mail on May 29 (PRC time),
but this one happens to be caught on 20200528, which is still in the bisection
queue and leads to the noise. But new patches in mail will not be further
tested.

> 
> That said; yes, this patch is buggered, Rostedt already noted that on
> review Friday.
> _______________________________________________
> LKP mailing list -- lkp(a)lists.01.org
> To unsubscribe send an email to lkp-leave(a)lists.01.org

  reply	other threads:[~2020-06-02 11:51 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
2020-06-02 11:51   ` Philip Li [this message]
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=20200602115130.GA10863@intel.com \
    --to=philip.li@intel.com \
    --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.