linux-kernel - Re: [PATCH 0/3] Make rcutorture safe(r) for arm64

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: <0cabdd10-658e-4577-9b4e-5d4a2641360e@nvidia.com>
Date: Fri, 9 May 2025 09:18:00 -0400
From: Joel Fernandes <joelagnelf@...dia.com>
To: paulmck@...nel.org, rcu@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-team@...a.com, rostedt@...dmis.org
Subject: Re: [PATCH 0/3] Make rcutorture safe(r) for arm64



On 5/8/2025 7:42 PM, Paul E. McKenney wrote:
> Hello!
> 
> This series makes a few small updates to make rcutorture run better
> on arm64 servers.  Remaining issues include TREE07 .config issues
> that are addressed by Mark Rutland's porting of PREEMPT_LAZY to arm64
> and by upcoming work to handle the fact that arm64 kernels cannot be
> built with CONFIG_SMP=n.  In the meantime, the CONFIG_SMP=n issue can
> be worked around by explictly specifying the TREE01, TREE02, TREE03,
> TREE04, TREE05, TREE07, SRCU-L, SRCU-N, SRCU-P, TASKS01, TASKS03, RUDE01,
> TRACE01, and TRACE02 scenarios, preferably in a script.  (But if you
> want typing practice, don't let me stand in your way!)
> 
> 1.	Check for "Call trace:" as well as "Call Trace:".
> 
> 2.	Reduce TREE01 CPU overcommit.
> 
> 3.	Remove MAXSMP and CPUMASK_OFFSTACK from TREE01.
> 

These I will take for 6.16 and run some tests, since we're seeing these issues
on ARM. But let me know if you want to delay to 6.17. Thanks!