linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Qian Cai <cai@lca.pw>,
	tj@kernel.org, vdavydov.dev@gmail.com, hannes@cmpxchg.org,
	guro@fb.com, cl@linux.com, penberg@kernel.org,
	rientjes@google.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/slub: fix a deadlock in show_slab_objects()
Date: Tue, 8 Oct 2019 10:47:51 +0200	[thread overview]
Message-ID: <20191008084751.GD6681@dhcp22.suse.cz> (raw)
In-Reply-To: <20191007145902.a1ae6aac11c29d466a445a94@linux-foundation.org>

On Mon 07-10-19 14:59:02, Andrew Morton wrote:
> On Mon, 7 Oct 2019 10:16:21 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> 
> > On Fri 04-10-19 14:57:01, Michal Hocko wrote:
> > > On Fri 04-10-19 08:31:49, Qian Cai wrote:
> > > > Long time ago, there fixed a similar deadlock in show_slab_objects()
> > > > [1]. However, it is apparently due to the commits like 01fb58bcba63
> > > > ("slab: remove synchronous synchronize_sched() from memcg cache
> > > > deactivation path") and 03afc0e25f7f ("slab: get_online_mems for
> > > > kmem_cache_{create,destroy,shrink}"), this kind of deadlock is back by
> > > > just reading files in /sys/kernel/slab which will generate a lockdep
> > > > splat below.
> > > > 
> > > > Since the "mem_hotplug_lock" here is only to obtain a stable online node
> > > > mask while racing with NUMA node hotplug, in the worst case, the results
> > > > may me miscalculated while doing NUMA node hotplug, but they shall be
> > > > corrected by later reads of the same files.
> > > 
> > > I think it is important to mention that this doesn't expose the
> > > show_slab_objects to use-after-free. There is only a single path that
> > > might really race here and that is the slab hotplug notifier callback
> > > __kmem_cache_shrink (via slab_mem_going_offline_callback) but that path
> > > doesn't really destroy kmem_cache_node data structures.
> 
> Yes, I noted this during review.  It's a bit subtle and is worthy of
> more than a changelog note, I think.  How about this?
> 
> --- a/mm/slub.c~mm-slub-fix-a-deadlock-in-show_slab_objects-fix
> +++ a/mm/slub.c
> @@ -4851,6 +4851,10 @@ static ssize_t show_slab_objects(struct
>  	 * already held which will conflict with an existing lock order:
>  	 *
>  	 * mem_hotplug_lock->slab_mutex->kernfs_mutex
> +	 *
> +	 * We don't really need mem_hotplug_lock (to hold off
> +	 * slab_mem_going_offline_callback()) here because slab's memory hot
> +	 * unplug code doesn't destroy the kmem_cache->node[] data.
>  	 */

Yes please! 

>  #ifdef CONFIG_SLUB_DEBUG
> _
> 
> > Andrew, please add this to the changelog so that we do not have to
> > scratch heads again when looking into that code.
> 
> I did that as well.

Thanks!
-- 
Michal Hocko
SUSE Labs


      reply	other threads:[~2019-10-08  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 12:31 [PATCH v2] mm/slub: fix a deadlock in show_slab_objects() Qian Cai
2019-10-04 12:57 ` Michal Hocko
2019-10-07  8:16   ` Michal Hocko
2019-10-07 21:59     ` Andrew Morton
2019-10-08  8:47       ` Michal Hocko [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=20191008084751.GD6681@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cai@lca.pw \
    --cc=cl@linux.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=vdavydov.dev@gmail.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).