linux-kernel - Re: [PATCH v8 2/2] slub: Introduce CONFIG_SLUB_RCU

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

Message-ID: <5qdsfymdkyqhc57ww64mphrshgq4ioelbtg3ojwpicmyzwjydw@kgzio5qsmnng>
Date: Tue, 13 Aug 2024 23:59:26 +0000
From: Shinichiro Kawasaki <shinichiro.kawasaki@....com>
To: Jann Horn <jannh@...gle.com>
CC: Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko
	<glider@...gle.com>, Andrey Konovalov <andreyknvl@...il.com>, Dmitry Vyukov
	<dvyukov@...gle.com>, Vincenzo Frascino <vincenzo.frascino@....com>, Andrew
 Morton <akpm@...ux-foundation.org>, Christoph Lameter <cl@...ux.com>, Pekka
 Enberg <penberg@...nel.org>, David Rientjes <rientjes@...gle.com>, Joonsoo
 Kim <iamjoonsoo.kim@....com>, Vlastimil Babka <vbabka@...e.cz>, Roman
 Gushchin <roman.gushchin@...ux.dev>, Hyeonggon Yoo <42.hyeyoo@...il.com>,
	Marco Elver <elver@...gle.com>, "kasan-dev@...glegroups.com"
	<kasan-dev@...glegroups.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
	David Sterba <dsterba@...e.cz>,
	"syzbot+263726e59eab6b442723@...kaller.appspotmail.com"
	<syzbot+263726e59eab6b442723@...kaller.appspotmail.com>
Subject: Re: [PATCH v8 2/2] slub: Introduce CONFIG_SLUB_RCU_DEBUG

On Aug 13, 2024 / 16:35, Jann Horn wrote:
[...]
> In the version you tested
> (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/tree/mm/slub.c?h=next-20240808#n4550),
> I made a mistake and wrote "if (WARN_ON(is_kfence_address(rcu_head)))"
> instead of "if (WARN_ON(is_kfence_address(object)))". That issue was
> fixed in v6 of the series after syzbot and the Intel test bot ran into
> the same issue.

Ah, I overlooked that 'rcu_head' has changed to 'object'... I should have
checked the patch change history. Good to know that the WARN is already fixed.
Thank you for the clarification.