linux-kernel - Re: [ BUG: Invalid wait context ] rtc_lock at: mc146818_avoid

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]

Message-ID: <87r029uh3j.ffs@tglx>
Date: Thu, 03 Apr 2025 22:26:24 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Borislav Petkov <bp@...en8.de>, linux-rtc@...r.kernel.org, Alexandre
 Belloni <alexandre.belloni@...tlin.com>, Mateusz Jończyk
 <mat.jonczyk@...pl>, lkml <linux-kernel@...r.kernel.org>, Anna-Maria
 Behnsen <anna-maria@...utronix.de>, Frederic Weisbecker
 <frederic@...nel.org>, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [ BUG: Invalid wait context ] rtc_lock at: mc146818_avoid_UIP

On Thu, Apr 03 2025 at 21:36, Sebastian Andrzej Siewior wrote:
> On 2025-04-03 15:50:32 [+0200], To Thomas Gleixner wrote:
>> > I wonder, why this splat hasn't popped before. On RT lockdep should have
>> > complained forever. Sebastian???
>> 
>> I sure haven't seen it. But it has to.
>
> might_sleep() is quite because system_states is SYSTEM_SUSPEND.
> lockdep seems to be quiet because I don't have an outer lock while
> testing via
> 	echo mem > /sys/power/state

Right. freeze triggers the suspend to idle path

> it is just
> | WARNING: CPU: 0 PID: 1007 at kernel/time/timekeeping.c:1858 timekeeping_suspend+0x3b/0x330

Which kernel version is that? I don't see a warning in timekeeping_suspend()

Thanks,

        tglx