[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZcZbP-PNG9BZfoOr9UEoqxqLkCviS8ooWOLc4Vp9+XimA@mail.gmail.com>
Date: Sat, 3 Aug 2024 00:40:37 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: Jann Horn <jannh@...gle.com>
Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko <glider@...gle.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, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, syzbot+263726e59eab6b442723@...kaller.appspotmail.com
Subject: Re: [PATCH v6 2/2] slub: Introduce CONFIG_SLUB_RCU_DEBUG
On Fri, Aug 2, 2024 at 11:35 PM Jann Horn <jannh@...gle.com> wrote:
>
> > Ah, notice another thing: this test might fail of someone enables
> > CONFIG_SLUB_RCU_DEBUG with HW_TAGS, right? I think we need another
> > check here.
>
> Why? I realize that HW_TAGS can't detect UAF in a TYPESAFE_BY_RCU slab
> after an object has been reused, but here we do no other allocations,
> so the object should still be free. And the kmalloc_uaf test also
> doesn't check for HW_TAGS.
Ah, right, all should be good, I got myself confused, sorry.
Powered by blists - more mailing lists