From: Christoph Hellwig <hch@lst.de>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: kbusch@kernel.org, logang@deltatee.com, hch@lst.de,
linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [PATCH 2/3] nvme: move get/put ctrl into dev open/release
Date: Tue, 8 Sep 2020 10:52:02 +0200 [thread overview]
Message-ID: <20200908085202.GB17413@lst.de> (raw)
In-Reply-To: <20200904023929.5320-3-chaitanya.kulkarni@wdc.com>
On Thu, Sep 03, 2020 at 07:39:28PM -0700, Chaitanya Kulkarni wrote:
> Introduce nvme_dev_release ctrl file release callback and move ctrl get
> and put operations from target passthru into host core in ctrl open and
> release file operations respectively. This is needed to atomically
> get/put ctrl and get/put ctrl module refcount without using any locks.
Besides the comment from Logan: this doesn't move as said in the
subject but adds a reference. I think this should be patch 1 as it
is a fixed that will need backports further back.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-09-08 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 2:39 [PATCH 0/3] nvme: fix module ref count Oops Chaitanya Kulkarni
2020-09-04 2:39 ` [PATCH 1/3] nvme: decouple nvme_ctrl_get_by_path() Chaitanya Kulkarni
2020-09-04 15:54 ` Logan Gunthorpe
2020-09-05 7:20 ` Christoph Hellwig
2020-09-05 22:57 ` Chaitanya Kulkarni
2020-09-08 8:49 ` Christoph Hellwig
2020-09-08 15:36 ` Logan Gunthorpe
2020-09-04 2:39 ` [PATCH 2/3] nvme: move get/put ctrl into dev open/release Chaitanya Kulkarni
2020-09-04 15:55 ` Logan Gunthorpe
2020-09-08 8:52 ` Christoph Hellwig [this message]
2020-09-04 2:39 ` [PATCH 3/3] nvme-core: fix nvme module ref count Oops Chaitanya Kulkarni
2020-09-04 15:57 ` Logan Gunthorpe
2020-09-05 22:03 ` Chaitanya Kulkarni
2020-09-08 15:33 ` Logan Gunthorpe
2020-09-08 8:54 ` Christoph Hellwig
2020-09-08 8:54 ` 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=20200908085202.GB17413@lst.de \
--to=hch@lst.de \
--cc=chaitanya.kulkarni@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=sagi@grimberg.me \
/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).