linux-kernel - Re: [linux-next:master] [x86] 66fbf67705: kernel-selftests.kvm.hardware_disable

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] [day] [month] [year] [list]

Message-ID: <20250221090008.5aWGygvI@linutronix.de>
Date: Fri, 21 Feb 2025 10:00:08 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Marco Elver <elver@...gle.com>
Cc: Oliver Sang <oliver.sang@...el.com>, oe-lkp@...ts.linux.dev,
	lkp@...el.com, Petr Pavlu <petr.pavlu@...e.com>,
	"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Ingo Molnar <mingo@...hat.com>,
	Josh Poimboeuf <jpoimboe@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	kasan-dev@...glegroups.com, linux-hardening@...r.kernel.org,
	Andrey Ryabinin <ryabinin.a.a@...il.com>,
	Kees Cook <kees@...nel.org>,
	Alexander Potapenko <glider@...gle.com>,
	Andrey Konovalov <andreyknvl@...il.com>,
	Dmitry Vyukov <dvyukov@...gle.com>,
	Vincenzo Frascino <vincenzo.frascino@....com>,
	Waiman Long <longman@...hat.com>
Subject: Re: [linux-next:master] [x86] 66fbf67705:
 kernel-selftests.kvm.hardware_disable_test.fail

On 2025-02-20 17:30:22 [+0100], Marco Elver wrote:
> > How much do we care here? Is this something that makes UBSAN + KASAN
> > folks uncomfortable? Or is lockdep slowing things down anyway?
> 
> Does this series from Waiman help?
> https://lore.kernel.org/all/20250213200228.1993588-4-longman@redhat.com/

I have applied

| locking/lock_events: Add locking events for rtmutex slow paths
| locking/lock_events: Add locking events for lockdep
| locking/lockdep: Disable KASAN instrumentation of lockdep.c
| locking/lockdep: Add kasan_check_byte() check in lock_acquire()

and with this I am down to:

| ~# time ./hardware_disable_test
| Random seed: 0x6b8b4567
| 
| real    0m29.517s
| user    0m0.493s
| sys     0m10.891s

Which is the pre-RCU case. Yes, the series from Waiman helps. This is my
favorite solution.

Sebastian