From: David Sterba <dsterba@suse.cz>
To: Jann Horn <jannh@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Marco Elver <elver@google.com>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, David Sterba <dsterba@suse.cz>,
syzbot+263726e59eab6b442723@syzkaller.appspotmail.com
Subject: Re: [PATCH v8 0/2] allow KASAN to detect UAF in SLAB_TYPESAFE_BY_RCU slabs
Date: Fri, 9 Aug 2024 20:27:46 +0200 [thread overview]
Message-ID: <20240809182746.GB25962@twin.jikos.cz> (raw)
In-Reply-To: <20240809-kasan-tsbrcu-v8-0-aef4593f9532@google.com>
On Fri, Aug 09, 2024 at 05:36:54PM +0200, Jann Horn wrote:
> Changes in v8:
> - in patch 2/2:
> - move rcu_barrier() out of locked region (vbabka)
> - rearrange code in slab_free_after_rcu_debug (vbabka)
> - Link to v7: https://lore.kernel.org/r/20240808-kasan-tsbrcu-v7-0-0d0590c54ae6@google.com
>
> Changes in v7:
> - in patch 2/2:
> - clarify kconfig comment (Marco)
> - fix memory leak (vbabka and dsterba)
FWIW, I've retested v7 and got no OOM (caused by the leak), on KASAN,
KFENCE and other debugging options enabled.
prev parent reply other threads:[~2024-08-09 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:36 Jann Horn
2024-08-09 15:36 ` [PATCH v8 1/2] kasan: catch invalid free before SLUB reinitializes the object Jann Horn
2024-08-09 15:36 ` [PATCH v8 2/2] slub: Introduce CONFIG_SLUB_RCU_DEBUG Jann Horn
2024-08-13 9:03 ` Shinichiro Kawasaki
2024-08-13 14:35 ` Jann Horn
2024-08-13 23:59 ` Shinichiro Kawasaki
2024-08-09 18:27 ` David Sterba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240809182746.GB25962@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=syzbot+263726e59eab6b442723@syzkaller.appspotmail.com \
--cc=vbabka@suse.cz \
--cc=vincenzo.frascino@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox