[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30a2e4babdcb22974a0a5ae8c5e764d951eef7dc.camel@fb.com>
Date: Thu, 21 Nov 2019 20:43:01 +0000
From: Rik van Riel <riel@...com>
To: Roman Gushchin <guro@...com>,
Christian Borntraeger <borntraeger@...ibm.com>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"hannes@...xchg.org" <hannes@...xchg.org>,
Kernel Team <Kernel-team@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"longman@...hat.com" <longman@...hat.com>,
"shakeelb@...gle.com" <shakeelb@...gle.com>,
"vdavydov.dev@...il.com" <vdavydov.dev@...il.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Janosch Frank <frankja@...ux.ibm.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: WARNING bisected (was Re: [PATCH v7 08/10] mm: rework non-root
kmem_cache lifecycle management)
On Thu, 2019-11-21 at 13:45 -0500, Roman Gushchin wrote:
> On Thu, Nov 21, 2019 at 05:59:54PM +0100, Christian Borntraeger
> wrote:
> >
> >
> > Yes, rmmod has to be called directly after the guest shutdown to
> > see the issue.
> > See my 2nd mail.
>
> I see. Do you know, which kmem_cache it is? If not, can you, please,
> figure it out?
>
> I tried to reproduce the issue, but wasn't successful so far. So I
> wonder
> what can make your case special.
I do not know either, but have a guess.
My guess would be that either the slab object or the
slab page is RCU freed, and the kmem_cache destruction
is called before that RCU callback has completed.
Powered by blists - more mailing lists