From: Simon Horman <horms@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Tycho Andersen <tycho@tycho.pizza>,
Vlastimil Babka <vbabka@suse.cz>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
jvoisin <julien.voisin@dustri.org>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, "GONG, Ruiqi" <gongruiqi@huaweicloud.com>,
Xiu Jianfeng <xiujianfeng@huawei.com>,
Suren Baghdasaryan <surenb@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Jann Horn <jannh@google.com>,
Matteo Rizzo <matteorizzo@google.com>,
Thomas Graf <tgraf@suug.ch>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v4 4/6] mm/slab: Introduce kmem_buckets_create() and family
Date: Wed, 5 Jun 2024 20:54:33 +0100 [thread overview]
Message-ID: <20240605195433.GA791188@kernel.org> (raw)
In-Reply-To: <202406041749.27CAE270@keescook>
On Tue, Jun 04, 2024 at 05:49:20PM -0700, Kees Cook wrote:
> On Tue, Jun 04, 2024 at 04:13:32PM -0600, Tycho Andersen wrote:
> > On Tue, Jun 04, 2024 at 04:02:28PM +0100, Simon Horman wrote:
> > > On Fri, May 31, 2024 at 12:14:56PM -0700, Kees Cook wrote:
> > > > + for (idx = 0; idx < ARRAY_SIZE(kmalloc_caches[KMALLOC_NORMAL]); idx++) {
> > > > + char *short_size, *cache_name;
> > > > + unsigned int cache_useroffset, cache_usersize;
> > > > + unsigned int size;
> > > > +
> > > > + if (!kmalloc_caches[KMALLOC_NORMAL][idx])
> > > > + continue;
> > > > +
> > > > + size = kmalloc_caches[KMALLOC_NORMAL][idx]->object_size;
> > > > + if (!size)
> > > > + continue;
> > > > +
> > > > + short_size = strchr(kmalloc_caches[KMALLOC_NORMAL][idx]->name, '-');
> > > > + if (WARN_ON(!short_size))
> > > > + goto fail;
> > > > +
> > > > + cache_name = kasprintf(GFP_KERNEL, "%s-%s", name, short_size + 1);
> > > > + if (WARN_ON(!cache_name))
> > > > + goto fail;
> > > > +
> > > > + if (useroffset >= size) {
> > > > + cache_useroffset = 0;
> > > > + cache_usersize = 0;
> > > > + } else {
> > > > + cache_useroffset = useroffset;
> > > > + cache_usersize = min(size - cache_useroffset, usersize);
> > > > + }
> > > > + (*b)[idx] = kmem_cache_create_usercopy(cache_name, size,
> > > > + align, flags, cache_useroffset,
> > > > + cache_usersize, ctor);
> > > > + kfree(cache_name);
> > > > + if (WARN_ON(!(*b)[idx]))
> > > > + goto fail;
> > > > + }
> > > > +
> > > > + return b;
> > > > +
> > > > +fail:
> > > > + for (idx = 0; idx < ARRAY_SIZE(kmalloc_caches[KMALLOC_NORMAL]); idx++) {
> > > > + if ((*b)[idx])
> > > > + kmem_cache_destroy((*b)[idx]);
> > >
> > > nit: I don't think it is necessary to guard this with a check for NULL.
> >
> > Isn't it? What if a kasprintf() fails halfway through the loop?
>
> He means that kmem_cache_destroy() already checks for NULL. Quite right!
>
> void kmem_cache_destroy(struct kmem_cache *s)
> {
> int err = -EBUSY;
> bool rcu_set;
>
> if (unlikely(!s) || !kasan_check_byte(s))
> return;
Yes, thanks. That is what I was referring to.
next prev parent reply other threads:[~2024-06-05 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 19:14 [PATCH v4 0/6] slab: Introduce dedicated bucket allocator Kees Cook
2024-05-31 19:14 ` [PATCH v4 1/6] mm/slab: Introduce kmem_buckets typedef Kees Cook
2024-05-31 19:14 ` [PATCH v4 2/6] mm/slab: Plumb kmem_buckets into __do_kmalloc_node() Kees Cook
2024-06-03 17:06 ` Vlastimil Babka
2024-06-03 22:44 ` Kees Cook
2024-06-04 12:30 ` Vlastimil Babka
2024-05-31 19:14 ` [PATCH v4 3/6] mm/slab: Introduce kvmalloc_buckets_node() that can take kmem_buckets argument Kees Cook
2024-05-31 19:14 ` [PATCH v4 4/6] mm/slab: Introduce kmem_buckets_create() and family Kees Cook
2024-06-04 15:02 ` Simon Horman
2024-06-04 22:13 ` Tycho Andersen
2024-06-05 0:49 ` Kees Cook
2024-06-05 19:54 ` Simon Horman [this message]
2024-05-31 19:14 ` [PATCH v4 5/6] ipc, msg: Use dedicated slab buckets for alloc_msg() Kees Cook
2024-05-31 19:14 ` [PATCH v4 6/6] mm/util: Use dedicated slab buckets for memdup_user() 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=20240605195433.GA791188@kernel.org \
--to=horms@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=gongruiqi@huaweicloud.com \
--cc=herbert@gondor.apana.org.au \
--cc=iamjoonsoo.kim@lge.com \
--cc=jannh@google.com \
--cc=julien.voisin@dustri.org \
--cc=kees@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matteorizzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=surenb@google.com \
--cc=tgraf@suug.ch \
--cc=tycho@tycho.pizza \
--cc=vbabka@suse.cz \
--cc=xiujianfeng@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.