linux-kernel - Re: [ANNOUNCE] v6.8-rc4-rt4

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: <1ae5b9e6-9eb4-49a5-8cfc-46359c8d74c3@arm.com>
Date: Fri, 23 Feb 2024 10:52:57 +0100
From: Pierre Gondois <pierre.gondois@....com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-rt-users@...r.kernel.org,
 Steven Rostedt <rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] v6.8-rc4-rt4

Hello Sebastian,,

On 2/14/24 17:11, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
> 
> I'm pleased to announce the v6.8-rc4-rt4 patch set.
> 
> Changes since v6.8-rc4-rt3:
> 
>    - The previous releases introduced a compiler warning for i915 driver
>      in the !i915 case. Reported by the kernel test robot.
> 
>    - An update to the printk series by John Ogness:
> 
>      - document new nbcon console callbacks:
>      
>      - add "threadprintk" boot argument for !PREEMPT_RT users that want a
>        fully threaded printk.
>      
>      - use thread callback (instead of atomic callback) for legacy printing
>        in task context.
>      
>      - sync with recently reviewed printk series.
> 
> Known issues
>       Pierre Gondois reported crashes on ARM64 together with "rtla timerlat
>       hist" as trigger. It is not yet understood. The report is at
> 	https://lore.kernel.org/70c08728-3d4f-47a6-8a3e-114e4877d120@arm.com

I recently tried to reproduce the issue using the same kernel version and platform,
but even after multiple resets and attempts to re-trigger it didn't show up.
As it doesn't seem anyone else reported anything similar, would it make sense
to drop the reference ?

Regards,
Pierre