[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200402095812.2t2rgx72n3xy35k2@linutronix.de>
Date: Thu, 2 Apr 2020 11:58:12 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: kernel test robot <lkp@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, rcu@...r.kernel.org,
LKP <lkp@...ts.01.org>
Subject: Re: de8f5e4f2d ("lockdep: Introduce wait-type checks"): [ 17.344674]
EIP: default_idle
On 2020-04-02 11:40:52 [+0200], Thomas Gleixner wrote:
> kernel test robot <lkp@...el.com> writes:
> > Greetings,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >
> > commit de8f5e4f2dc1f032b46afda0a78cab5456974f89
> > Author: Peter Zijlstra <peterz@...radead.org>
> > AuthorDate: Sat Mar 21 12:26:01 2020 +0100
> > Commit: Peter Zijlstra <peterz@...radead.org>
> > CommitDate: Sat Mar 21 16:00:24 2020 +0100
> >
> > lockdep: Introduce wait-type checks
>
> Can you please avoid enabling
>
> > CONFIG_PROVE_RAW_LOCK_NESTING=y
>
> for now?
>
> As the changelog states, there are known issues and that's why the
> config is default=n.
There is that. What puzzled me for a little while was the part that the
call chain itself is *valid* and should not trigger this. After staring
at it for a while I noticed that the test was performed *before* the
hrtimer bits were merged.
> Thanks,
>
> tglx
Sebastian
Powered by blists - more mailing lists