From: hch@infradead.org (Christoph Hellwig)
Subject: Kernel v4.19-rc4 KASAN complaint
Date: Fri, 5 Oct 2018 00:34:27 -0700 [thread overview]
Message-ID: <20181005073427.GA7075@infradead.org> (raw)
In-Reply-To: <20180920173625.GB31127@localhost.localdomain>
On Thu, Sep 20, 2018@11:36:25AM -0600, Keith Busch wrote:
> > > 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.
>
> Nice, thanks for confirming. I'll send a proper patch, but also wonder
> why the error doesn't show up in 4.18.
Independent of fixing the issue Bart reported this looks like a good
fix, can you send a proper patch for it?
next prev parent reply other threads:[~2018-10-05 7:34 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 [this message]
2018-09-20 17:36 ` Bart Van Assche
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=20181005073427.GA7075@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).