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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240613150142.GHZmsJ1haFMVkHHjEE@fat_crate.local>
Date: Thu, 13 Jun 2024 17:01:42 +0200
From: Borislav Petkov <bp@...en8.de>
To: Anna-Maria Behnsen <anna-maria@...utronix.de>,
	Narasimhan V <Narasimhan.V@....com>
Cc: Frederic Weisbecker <frederic@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 7 PID: 0 at kernel/time/timer_migration.c:1332
 tmigr_inactive_up+0xd2/0x190

Hi Anna-Maria,

On Thu, Jun 13, 2024 at 04:40:33PM +0200, Anna-Maria Behnsen wrote:
> thanks for the report. Is it reproducible?

Narasimhan just tells me that he was NOT able to reproduce it in today's run.
I guess we can wait and see.

> If yes, might it be possible to enable the timer_migration tracepoints and
> provide the trace?

Can you pls give Narasimhan exact instructions what to do the next time it
happens?

@Narasimhan: when you see it next time, you should try to run Anna-Maria's trace
with the same exact kernel and send results.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ