From: Muchun Song <songmuchun@bytedance.com>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH 1/3] mm/slub: Fix slabs_node return value when CONFIG_SLUB_DEBUG disabled
Date: Mon, 15 Jun 2020 14:26:16 +0800 [thread overview]
Message-ID: <CAMZfGtUvGEzrXTUBnrGnFzxU_L2D5_YPV_n_a2VLiPN9MeJLwA@mail.gmail.com> (raw)
In-Reply-To: <CAAmzW4Opfu7_r3UdjTKYui15u2kdwp9Y2-aje30iZ_LsQ0tHwA@mail.gmail.com>
On Mon, Jun 15, 2020 at 2:11 PM Joonsoo Kim <js1304@gmail.com> wrote:
>
> 2020년 6월 14일 (일) 오후 9:39, Muchun Song <songmuchun@bytedance.com>님이 작성:
> >
> > The slabs_node() always return zero when CONFIG_SLUB_DEBUG is disabled.
> > But some codes determine whether slab is empty by checking the return
> > value of slabs_node(). As you know, the result is not correct. This
> > problem can be reproduce by the follow code(and boot system with the
> > cmdline of "slub_nomerge"):
> >
> > void *objs[32];
> > struct kmem_cache *cache = kmem_cache_create("kmem-test", 128, 0,
> > 0, 0);
> >
> > if (cache) {
> > int i;
> >
> > /* Make a full slab */
> > for (i = 0; i < ARRAY_SIZE(objs); i++)
> > objs[i] = kmem_cache_alloc(cache, GFP_KERNEL_ACCOUNT);
> >
> > /*
> > * This really should fail because the slab cache still has
> > * objects. But we did destroy the @cache because of zero
> > * returned by slabs_node().
> > */
> > kmem_cache_destroy(cache);
> > }
> >
> > To fix it, we can move the nr_slabs of kmem_cache_node out of the
> > CONFIG_SLUB_DEBUG. So we can get the corrent value returned by the
> > slabs_node().
> >
> > With this patch applied, we will get a warning message and stack
> > trace in the dmesg.
> >
> > Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> > ---
> > mm/slab.h | 2 +-
> > mm/slub.c | 80 +++++++++++++++++++++++++++++++++------------------------------
> > 2 files changed, 43 insertions(+), 39 deletions(-)
> >
> > diff --git a/mm/slab.h b/mm/slab.h
> > index 0b91f2a7b033..062d4542b7e2 100644
> > --- a/mm/slab.h
> > +++ b/mm/slab.h
> > @@ -619,8 +619,8 @@ struct kmem_cache_node {
> > #ifdef CONFIG_SLUB
> > unsigned long nr_partial;
> > struct list_head partial;
> > -#ifdef CONFIG_SLUB_DEBUG
> > atomic_long_t nr_slabs;
> > +#ifdef CONFIG_SLUB_DEBUG
> > atomic_long_t total_objects;
> > struct list_head full;
> > #endif
> > diff --git a/mm/slub.c b/mm/slub.c
> > index 49b5cb7da318..1a3e6a5b7287 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
>
> Hello,
>
> You also need to initialize nr_slabs in init_kmem_cache_node()
> on !CONFIG_SLUB_DEBUG.
Good catch, thanks! I will fix it in the next version.
>
> Otherwise, looks good to me.
>
> Thanks.
--
Yours,
Muchun
next prev parent reply other threads:[~2020-06-15 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 12:39 [PATCH 0/3] mm/slub: Fix slabs_node return value Muchun Song
2020-06-14 12:39 ` [PATCH 1/3] mm/slub: Fix slabs_node return value when CONFIG_SLUB_DEBUG disabled Muchun Song
2020-06-15 6:11 ` Joonsoo Kim
2020-06-15 6:26 ` Muchun Song [this message]
2020-06-15 16:46 ` Vlastimil Babka
2020-06-14 12:39 ` [PATCH 2/3] mm/slub: Use node_nr_slabs() instead of slabs_node() Muchun Song
2020-06-15 6:15 ` Joonsoo Kim
2020-06-15 6:20 ` [External] " Muchun Song
2020-06-14 12:39 ` [PATCH 3/3] mm/slub: Fix release all resources used by a slab cache Muchun Song
2020-06-15 6:23 ` Joonsoo Kim
2020-06-15 6:41 ` [External] " Muchun Song
2020-06-15 7:25 ` Joonsoo Kim
2020-06-15 7:50 ` Muchun Song
2020-06-17 16:19 ` [PATCH 0/3] mm/slub: Fix slabs_node return value Christopher Lameter
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=CAMZfGtUvGEzrXTUBnrGnFzxU_L2D5_YPV_n_a2VLiPN9MeJLwA@mail.gmail.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).