From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/2] nvme: fixup crash in device_add_disk()
Date: Tue, 19 Feb 2019 13:13:56 +0100 [thread overview]
Message-ID: <20190219121358.57975-1-hare@suse.de> (raw)
Hi all,
during testing we've ran into an issue where the system would crash
in device_add_disk(); analysis showed that there is a race condition
in nvme_validate_ns() if called simultaneously for the same controller.
This patchset tries to fix it up.
As usual, comments and reviews are appreciated.
Hannes Reinecke (2):
nvme: return error from nvme_alloc_ns()
nvme: protect against race condition in nvme_validate_ns()
drivers/nvme/host/core.c | 51 ++++++++++++++++++++++++++++++++++++------------
1 file changed, 38 insertions(+), 13 deletions(-)
--
2.16.4
next reply other threads:[~2019-02-19 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 12:13 Hannes Reinecke [this message]
2019-02-19 12:13 ` [PATCH 1/2] nvme: return error from nvme_alloc_ns() Hannes Reinecke
2019-02-19 19:42 ` Sagi Grimberg
2019-02-20 14:21 ` Christoph Hellwig
2019-02-19 12:13 ` [PATCH 2/2] nvme: protect against race condition in nvme_validate_ns() Hannes Reinecke
2019-02-19 19:44 ` Sagi Grimberg
2019-02-19 19:54 ` Keith Busch
2019-02-20 6:52 ` Hannes Reinecke
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=20190219121358.57975-1-hare@suse.de \
--to=hare@suse.de \
/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