From: hch@infradead.org (Christoph Hellwig)
Subject: Kernel v4.19-rc4 KASAN complaint
Date: Mon, 8 Oct 2018 03:13:23 -0700 [thread overview]
Message-ID: <20181008101323.GA29380@infradead.org> (raw)
In-Reply-To: <20181008061152.GA18836@X58A-UD3R>
On Mon, Oct 08, 2018@03:11:52PM +0900, Byungchul Park wrote:
> Is it ok to call nvme_mpath_clear_current_path(ns) without holding
> any lock in nvme_failover_req(req)? No possible to race with other
> rcu_assign_pointer(ns->head->current_path, some_value)?
We can race with an assignment, but it should be harmless, as that
call is just an optimization to get everyone to stop using the
path ASAP. If we actually free the namespace we always go through
nvme_ns_remove, which calls nvme_mpath_clear_current_path under
subsys->lock.
next prev parent reply other threads:[~2018-10-08 10:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181006170915.GS2674@linux.ibm.com>
[not found] ` <31b80bc0-afc6-6bd9-c722-302f538d3e5b@lge.com>
2018-10-08 6:11 ` Kernel v4.19-rc4 KASAN complaint Byungchul Park
2018-10-08 10:13 ` Christoph Hellwig [this message]
2018-09-18 21:16 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
2018-09-20 17:45 ` Keith Busch
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=20181008101323.GA29380@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).