From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH 1/4] nvme: fix srcu locking on error return in nvme_get_ns_from_disk
Date: Thu, 16 May 2019 13:01:22 -0600 [thread overview]
Message-ID: <20190516190122.GA23669@localhost.localdomain> (raw)
In-Reply-To: <20190516185036.17394-1-hch@lst.de>
On Thu, May 16, 2019@08:50:33PM +0200, Christoph Hellwig wrote:
> If we can't get a namespace don't leak the SRCU lock. nvme_ioctl was
> working around this, but nvme_pr_command wasn't handling this properly.
> Just do what callers would usually expect.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Looks good.
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2019-05-16 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 18:50 [PATCH 1/4] nvme: fix srcu locking on error return in nvme_get_ns_from_disk Christoph Hellwig
2019-05-16 18:50 ` [PATCH 2/4] nvme: remove the ifdef around nvme_nvm_ioctl Christoph Hellwig
2019-05-16 19:01 ` Keith Busch
2019-05-16 22:33 ` Chaitanya Kulkarni
2019-05-16 18:50 ` [PATCH 3/4] nvme: merge nvme_ns_ioctl into nvme_ioctl Christoph Hellwig
2019-05-16 19:02 ` Keith Busch
2019-05-16 22:40 ` Chaitanya Kulkarni
2019-05-16 18:50 ` [PATCH 4/4] nvme: release namespace SRCU protection before performing controller ioctls Christoph Hellwig
2019-05-16 19:05 ` Keith Busch
2019-05-16 22:57 ` Chaitanya Kulkarni
2019-05-16 19:01 ` Keith Busch [this message]
2019-05-16 22:33 ` [PATCH 1/4] nvme: fix srcu locking on error return in nvme_get_ns_from_disk Chaitanya Kulkarni
-- strict thread matches above, loose matches on Subject: below --
2019-05-17 9:47 Christoph Hellwig
2019-05-17 18:36 ` 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=20190516190122.GA23669@localhost.localdomain \
--to=kbusch@kernel.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.