[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9q3Cwba4Z=cnosOrDUAWEHtYQ9FZ6hsDpOS4czvc6DJJg@mail.gmail.com>
Date: Tue, 19 Jun 2018 15:40:26 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Shakeel Butt <shakeelb@...gle.com>, aryabinin@...tuozzo.com,
Alexander Potapenko <glider@...gle.com>, cl@...ux.com,
penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
Andrew Morton <akpm@...ux-foundation.org>,
kasan-dev@...glegroups.com, Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Possible regression in "slab, slub: skip unnecessary kasan_cache_shutdown()"
On Tue, Jun 19, 2018 at 3:31 PM Dmitry Vyukov <dvyukov@...gle.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. :)
Powered by blists - more mailing lists