From: bvanassche@acm.org (Bart Van Assche)
Subject: Kernel v4.19-rc4 KASAN complaint
Date: Thu, 20 Sep 2018 10:36:30 -0700 [thread overview]
Message-ID: <1537464990.224533.13.camel@acm.org> (raw)
In-Reply-To: <1537464689.224533.10.camel@acm.org>
On Thu, 2018-09-20@10:31 -0700, Bart Van Assche wrote:
> On Thu, 2018-09-20@11:01 -0600, Keith Busch wrote:
> > On Tue, Sep 18, 2018@02:16:48PM -0700, Bart Van Assche wrote:
> > > Hello,
> > >
> > > If I run the nvmeof-mp tests from https://github.com/bvanassche/blktests
> > > against kernel v4.19-rc4 then a KASAN complaint appears. This complaint does
> > > not appear when I run these tests against kernel v4.18. Could this be a
> > > regression?
> >
> > Not sure if the following is what you're hitting since it wouldn't be a
> > regression. It looks like removing a namespace path and clearing it as
> > the current path is in the wrong order, such that the very next IO
> > may reference the namespace being deleted.
> >
> > ---
> > diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> > index 893f1fcc17cd..a01b6743d62b 100644
> > --- a/drivers/nvme/host/core.c
> > +++ b/drivers/nvme/host/core.c
> > @@ -3143,8 +3143,8 @@ static void nvme_ns_remove(struct nvme_ns *ns)
> > }
> >
> > mutex_lock(&ns->ctrl->subsys->lock);
> > - nvme_mpath_clear_current_path(ns);
> > list_del_rcu(&ns->siblings);
> > + nvme_mpath_clear_current_path(ns);
> > mutex_unlock(&ns->ctrl->subsys->lock);
> >
> > down_write(&ns->ctrl->namespaces_rwsem);
>
> That patch makes the KASAN complaint disappear on my test setup.
Sorry, I spoke too soon. I didn't see it in the dmesg output because it
disappeared from that buffer but I found the complaint in the system log:
Sep 20 10:17:23 ubuntu-vm kernel: [ 144.820073] WARNING: possible circular locking dependency detected
Sep 20 10:17:23 ubuntu-vm kernel: [ 144.972667] Call Trace:
Sep 20 10:18:51 ubuntu-vm kernel: [ 232.585122] BUG: KASAN: use-after-free in srcu_invoke_callbacks+0x207/0x290
Sep 20 10:18:51 ubuntu-vm kernel: [ 232.585146] Call Trace:
Sep 20 10:28:02 ubuntu-vm kernel: [ 58.755492] WARNING: possible circular locking dependency detected
Sep 20 10:28:02 ubuntu-vm kernel: [ 58.825452] Call Trace:
Sep 20 10:31:44 ubuntu-vm kernel: [ 281.520737] BUG: KASAN: use-after-free in srcu_invoke_callbacks+0x207/0x290
Sep 20 10:31:44 ubuntu-vm kernel: [ 281.538488] Call Trace:
Bart.
next prev parent reply other threads:[~2018-09-20 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 21:16 Kernel v4.19-rc4 KASAN complaint Bart Van Assche
2018-09-20 7:10 ` Christoph Hellwig
2018-09-20 17:24 ` Bart Van Assche
2018-09-25 23:32 ` Christoph Hellwig
2018-09-26 3:14 ` Paul E. McKenney
2018-10-05 7:38 ` Christoph Hellwig
2018-10-17 6:39 ` Christoph Hellwig
2018-10-17 14:38 ` Bart Van Assche
2018-10-17 17:32 ` Bart Van Assche
2018-09-24 4:27 ` Sagi Grimberg
2018-09-24 14:04 ` Bart Van Assche
2018-09-20 17:01 ` Keith Busch
2018-09-20 17:31 ` Bart Van Assche
2018-09-20 17:36 ` Keith Busch
2018-10-05 7:34 ` Christoph Hellwig
2018-09-20 17:36 ` Bart Van Assche [this message]
2018-09-20 17:45 ` Keith Busch
[not found] <20181006170915.GS2674@linux.ibm.com>
[not found] ` <31b80bc0-afc6-6bd9-c722-302f538d3e5b@lge.com>
2018-10-08 6:11 ` Byungchul Park
2018-10-08 10:13 ` Christoph Hellwig
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=1537464990.224533.13.camel@acm.org \
--to=bvanassche@acm.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.