From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Shakeel Butt <shakeelb@google.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Alexander Potapenko <glider@google.com>,
Greg Thelen <gthelen@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
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>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab, slub: skip unnecessary kasan_cache_shutdown()
Date: Wed, 28 Mar 2018 20:03:20 +0300 [thread overview]
Message-ID: <3d48de97-0e5f-eba4-0d66-32eb300b79c3@virtuozzo.com> (raw)
In-Reply-To: <20180327230603.54721-1-shakeelb@google.com>
On 03/28/2018 02:06 AM, Shakeel Butt wrote:
> The kasan quarantine is designed to delay freeing slab objects to catch
> use-after-free. The quarantine can be large (several percent of machine
> memory size). When kmem_caches are deleted related objects are flushed
> from the quarantine but this requires scanning the entire quarantine
> which can be very slow. We have seen the kernel busily working on this
> while holding slab_mutex and badly affecting cache_reaper, slabinfo
> readers and memcg kmem cache creations.
>
> It can easily reproduced by following script:
>
> yes . | head -1000000 | xargs stat > /dev/null
> for i in `seq 1 10`; do
> seq 500 | (cd /cg/memory && xargs mkdir)
> seq 500 | xargs -I{} sh -c 'echo $BASHPID > \
> /cg/memory/{}/tasks && exec stat .' > /dev/null
> seq 500 | (cd /cg/memory && xargs rmdir)
> done
>
> The busy stack:
> kasan_cache_shutdown
> shutdown_cache
> memcg_destroy_kmem_caches
> mem_cgroup_css_free
> css_free_rwork_fn
> process_one_work
> worker_thread
> kthread
> ret_from_fork
>
> This patch is based on the observation that if the kmem_cache to be
> destroyed is empty then there should not be any objects of this cache in
> the quarantine.
>
> Without the patch the script got stuck for couple of hours. With the
> patch the script completed within a second.
>
> Signed-off-by: Shakeel Butt <shakeelb@google.com>
>
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
next prev parent reply other threads:[~2018-03-28 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 23:06 Shakeel Butt
2018-03-28 0:16 ` David Rientjes
2018-03-28 5:41 ` Shakeel Butt
2018-03-28 21:29 ` David Rientjes
2018-03-28 17:03 ` Andrey Ryabinin [this message]
2018-03-28 22:00 ` 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=3d48de97-0e5f-eba4-0d66-32eb300b79c3@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gthelen@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--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
all inboxes | Powered by JetHome®