linux-kernel - Re: [RFC][PATCH] hrtimer: Use printk_deferred_once for hrtimer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 22 Feb 2024 08:45:51 -0800
From: John Stultz <jstultz@...gle.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, Frederic Weisbecker <frederic@...nel.org>, 
	Steven Rostedt <rostedt@...dmis.org>, kernel-team@...roid.com, 
	John Ogness <jogness@...utronix.de>
Subject: Re: [RFC][PATCH] hrtimer: Use printk_deferred_once for
 hrtimer_interrupt message

On Thu, Feb 22, 2024 at 7:17 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Wed, Feb 21 2024 at 21:12, John Stultz wrote:
>
> Cc+ John. Keeping context intact,
>
> > With qemu, I constantly see lockdep warnings after the
> > hrimter_interrupt message is printed:
> >
> > [   43.434557] hrtimer: interrupt took 6517564 ns
> > [   43.435000]
> > [   43.435000] =============================
> > [   43.435000] [ BUG: Invalid wait context ]
>
> Do you have PROVE_RAW_LOCK_NESTING enabled?

Yes, I do. Let me know if there's anything else you'd like me to try.

thanks
-john