From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 0/5] Misc NVMe lockdep fixes
Date: Tue, 15 May 2018 09:40:38 +0200 [thread overview]
Message-ID: <20180515074043.22843-1-jthumshirn@suse.de> (raw)
I've "accidently" activated lockdep and ran some tests on nvme, here's
the post-fallout patch series.
Johannes Thumshirn (5):
nvme: fix lockdep warning in nvme_mpath_clear_current_path
nvme: don't hold nvmf_transports_rwsem for more than transport lookups
nvme: call nvmf_create_ctrl before checking for duplicate assignment
nvmet: use atomic allocations when allocating fc requests
nvmet: fcloop: use irqsave spinlocks
drivers/nvme/host/fabrics.c | 20 +++++++---------
drivers/nvme/host/nvme.h | 3 ++-
drivers/nvme/target/fcloop.c | 54 ++++++++++++++++++++++++--------------------
3 files changed, 40 insertions(+), 37 deletions(-)
--
2.16.3
next reply other threads:[~2018-05-15 7:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 7:40 Johannes Thumshirn [this message]
2018-05-15 7:40 ` [PATCHv2 1/5] nvme: fix lockdep warning in nvme_mpath_clear_current_path Johannes Thumshirn
2018-05-15 8:11 ` Christoph Hellwig
2018-05-31 9:22 ` Sagi Grimberg
2018-05-15 7:40 ` [PATCH 2/5] nvme: don't hold nvmf_transports_rwsem for more than transport lookups Johannes Thumshirn
2018-05-15 7:48 ` Christoph Hellwig
2018-05-31 9:24 ` Sagi Grimberg
2018-05-15 7:40 ` [PATCH 3/5] nvme: call nvmf_create_ctrl before checking for duplicate assignment Johannes Thumshirn
2018-05-15 7:50 ` Christoph Hellwig
2018-05-15 7:52 ` Johannes Thumshirn
2018-05-31 9:26 ` Sagi Grimberg
2018-05-15 7:40 ` [PATCH 4/5] nvmet: use atomic allocations when allocating fc requests Johannes Thumshirn
2018-05-31 9:31 ` Sagi Grimberg
2018-06-12 20:36 ` James Smart
2018-06-12 20:39 ` James Smart
2018-05-15 7:40 ` [PATCH 5/5] nvmet: fcloop: use irqsave spinlocks Johannes Thumshirn
2018-05-31 9:37 ` Sagi Grimberg
2018-06-12 20:41 ` James Smart
2018-06-12 20:48 ` Jens Axboe
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=20180515074043.22843-1-jthumshirn@suse.de \
--to=jthumshirn@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;
as well as URLs for NNTP newsgroup(s).