linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Shakeel Butt <shakeelb@google.com>,
	aryabinin@virtuozzo.com, Alexander Potapenko <glider@google.com>,
	cl@linux.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, Andrew Morton <akpm@linux-foundation.org>,
	kasan-dev@googlegroups.com, Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Possible regression in "slab, slub: skip unnecessary kasan_cache_shutdown()"
Date: Tue, 19 Jun 2018 15:40:26 +0200	[thread overview]
Message-ID: <CAHmME9q3Cwba4Z=cnosOrDUAWEHtYQ9FZ6hsDpOS4czvc6DJJg@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+b+9HK8Ti_iXA1DcHDeTR+Cj-xaQ+kQpvc7xPNafk5tkw@mail.gmail.com>

On Tue, Jun 19, 2018 at 3:31 PM Dmitry Vyukov <dvyukov@google.com> wrote:
> Since I already looked at the code, if init and uninit can be called
> concurrently, I think there is a prominent race condition between init
> and uninit: a concurrent uninit can run concurrnetly with the next
> init and this will totally mess things up.

Good point; fixed. Though this doesn't have any effect on the issue here. :)

  reply	other threads:[~2018-06-19 13:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  2:51 Jason A. Donenfeld
2018-06-19  3:59 ` Shakeel Butt
2018-06-19  4:08   ` Jason A. Donenfeld
2018-06-19  4:55     ` Dmitry Vyukov
2018-06-19 13:04       ` Jason A. Donenfeld
2018-06-19 13:16         ` Dmitry Vyukov
2018-06-19 15:08         ` Shakeel Butt
2018-06-19 15:18           ` Jason A. Donenfeld
2018-06-19 19:21             ` Shakeel Butt
2018-06-19 20:20               ` Jason A. Donenfeld
2018-06-19  5:06     ` Shakeel Butt
2018-06-19 13:25       ` Jason A. Donenfeld
2018-06-19 13:30         ` Dmitry Vyukov
2018-06-19 13:40           ` Jason A. Donenfeld [this message]
2018-06-19 17:34 ` Andrey Ryabinin
2018-06-19 20:17   ` Jason A. Donenfeld

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='CAHmME9q3Cwba4Z=cnosOrDUAWEHtYQ9FZ6hsDpOS4czvc6DJJg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=cl@linux.com \
    --cc=dvyukov@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=shakeelb@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