From: Feng Tang <feng.tang@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Marco Elver <elver@google.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>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
David Gow <davidgow@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
Alexander Potapenko <glider@google.com>,
"Andrey Ryabinin" <ryabinin.a.a@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kasan-dev@googlegroups.com" <kasan-dev@googlegroups.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH v2 0/5] mm/slub: Improve data handling of krealloc() when orig_size is enabled
Date: Mon, 14 Oct 2024 20:52:58 +0800 [thread overview]
Message-ID: <Zw0UKtx5d2hnHvDV@feng-clx.sh.intel.com> (raw)
In-Reply-To: <a34e6796-e550-465c-92dc-ee659716b918@suse.cz>
On Mon, Oct 14, 2024 at 10:53:32AM +0200, Vlastimil Babka wrote:
> On 10/14/24 09:52, Feng Tang wrote:
> > On Fri, Oct 04, 2024 at 05:52:10PM +0800, Vlastimil Babka wrote:
> > Thanks for the suggestion!
> >
> > As there were error report about the NULL slab for big kmalloc object, how
> > about the following code for
> >
> > __do_krealloc(const void *p, size_t new_size, gfp_t flags)
> > {
> > void *ret;
> > size_t ks = 0;
> > int orig_size = 0;
> > struct kmem_cache *s = NULL;
> >
> > /* Check for double-free. */
> > if (likely(!ZERO_OR_NULL_PTR(p))) {
> > if (!kasan_check_byte(p))
> > return NULL;
> >
> > ks = ksize(p);
>
> I think this will result in __ksize() doing
> skip_orig_size_check(folio_slab(folio)->slab_cache, object);
> and we don't want that?
I think that's fine. As later code will re-set the orig_size anyway.
> Also the checks below repeat some of the checks of ksize().
Yes, there is some redundancy, mostly the virt_to_slab()
> So I think in __do_krealloc() we should do things manually to determine ks
> and not call ksize(). Just not break any of the cases ksize() handles
> (kfence, large kmalloc).
OK, originally I tried not to expose internals of __ksize(). Let me
try this way.
Thanks,
Feng
>
> >
> > /* Some objects have no orig_size, like big kmalloc case */
> > if (is_kfence_address(p)) {
> > orig_size = kfence_ksize(p);
> > } else if (virt_to_slab(p)) {
> > s = virt_to_cache(p);
> > orig_size = get_orig_size(s, (void *)p);
> > }
> > } else {
> > goto alloc_new;
> > }
> >
> > /* If the object doesn't fit, allocate a bigger one */
> > if (new_size > ks)
> > goto alloc_new;
> >
> > /* Zero out spare memory. */
> > if (want_init_on_alloc(flags)) {
> > kasan_disable_current();
> > if (orig_size && orig_size < new_size)
> > memset((void *)p + orig_size, 0, new_size - orig_size);
> > else
> > memset((void *)p + new_size, 0, ks - new_size);
> > kasan_enable_current();
> > }
> >
> > /* Setup kmalloc redzone when needed */
> > if (s && slub_debug_orig_size(s) && !is_kfence_address(p)) {
> > set_orig_size(s, (void *)p, new_size);
> > if (s->flags & SLAB_RED_ZONE && new_size < ks)
> > memset_no_sanitize_memory((void *)p + new_size,
> > SLUB_RED_ACTIVE, ks - new_size);
> > }
> >
> > p = kasan_krealloc((void *)p, new_size, flags);
> > return (void *)p;
> >
> > alloc_new:
> > ret = kmalloc_node_track_caller_noprof(new_size, flags, NUMA_NO_NODE, _RET_IP_);
> > if (ret && p) {
> > /* Disable KASAN checks as the object's redzone is accessed. */
> > kasan_disable_current();
> > memcpy(ret, kasan_reset_tag(p), orig_size ?: ks);
> > kasan_enable_current();
> > }
> >
> > return ret;
> > }
next prev parent reply other threads:[~2024-10-14 12:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 6:45 Feng Tang
2024-09-11 6:45 ` [PATCH v2 1/5] mm/kasan: Don't store metadata inside kmalloc object when slub_debug_orig_size is on Feng Tang
2024-09-11 6:45 ` [PATCH v2 2/5] mm/slub: Consider kfence case for get_orig_size() Feng Tang
2024-09-11 6:45 ` [PATCH v2 3/5] mm/slub: Move krealloc() and related code to slub.c Feng Tang
2024-09-11 6:45 ` [PATCH v2 4/5] mm/slub: Improve redzone check and zeroing for krealloc() Feng Tang
2024-09-11 6:45 ` [PATCH v2 5/5] mm/slub, kunit: Add testcase for krealloc redzone and zeroing Feng Tang
2024-10-02 10:42 ` [PATCH v2 0/5] mm/slub: Improve data handling of krealloc() when orig_size is enabled Vlastimil Babka
2024-10-04 6:44 ` Marco Elver
2024-10-04 9:18 ` Vlastimil Babka
2024-10-04 9:52 ` Vlastimil Babka
2024-10-04 10:28 ` Feng Tang
2024-10-14 7:52 ` Feng Tang
2024-10-14 8:53 ` Vlastimil Babka
2024-10-14 12:52 ` Feng Tang [this message]
2024-10-14 13:12 ` Vlastimil Babka
2024-10-14 14:20 ` Feng Tang
2024-10-14 20:40 ` Kees Cook
2024-11-04 11:28 ` Feng Tang
2024-11-04 11:45 ` Vlastimil Babka
2024-11-04 12:37 ` Feng Tang
2024-10-14 20:35 ` Kees Cook
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=Zw0UKtx5d2hnHvDV@feng-clx.sh.intel.com \
--to=feng.tang@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cl@linux.com \
--cc=dakr@kernel.org \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.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=skhan@linuxfoundation.org \
--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