<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/nvme/target/loop.c, branch linux-4.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-04-12T10:31:07Z</updated>
<entry>
<title>nvme-fabrics: protect against module unload during create_ctrl</title>
<updated>2018-04-12T10:31:07Z</updated>
<author>
<name>Roy Shterman</name>
</author>
<published>2017-12-25T12:18:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2c624d6fede9a0c3f2ae66518ab0e9847b3bd4fe'/>
<id>urn:sha1:2c624d6fede9a0c3f2ae66518ab0e9847b3bd4fe</id>
<content type='text'>
[ Upstream commit 0de5cd367c6aa2a31a1c931628f778f79f8ef22e ]

NVMe transport driver module unload may (and usually does) trigger
iteration over the active controllers and delete them all (sometimes
under a mutex).  However, a controller can be created concurrently with
module unload which can lead to leakage of resources (most important char
device node leakage) in case the controller creation occured after the
unload delete and drain sequence.  To protect against this, we take a
module reference to guarantee that the nvme transport driver is not
unloaded while creating a controller.

Signed-off-by: Roy Shterman &lt;roys@lightbitslabs.com&gt;
Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: Max Gurtovoy &lt;maxg@mellanox.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nvme-loop: check if queue is ready in queue_rq</title>
<updated>2017-11-20T07:28:36Z</updated>
<author>
<name>Sagi Grimberg</name>
</author>
<published>2017-10-24T12:25:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9d7fab04b95e8c26014a9bfc1c943b8360b44c17'/>
<id>urn:sha1:9d7fab04b95e8c26014a9bfc1c943b8360b44c17</id>
<content type='text'>
In case the queue is not LIVE (fully functional and connected at the nvmf
level), we cannot allow any commands other than connect to pass through.

Add a new queue state flag NVME_LOOP_Q_LIVE which is set after nvmf connect
and cleared in queue teardown.

Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet: better data length validation</title>
<updated>2017-11-11T02:53:25Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2017-11-09T13:29:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5e62d5c993e6889cd314d5b5de6b670152109a0e'/>
<id>urn:sha1:5e62d5c993e6889cd314d5b5de6b670152109a0e</id>
<content type='text'>
Currently the NVMe target stores the expexted data length in req-&gt;data_len
and uses that for data transfer decisions, but that does not take the
actual transfer length in the SGLs into account.  So this adds a new
transfer_len field, into which the transport drivers store the actual
transfer length.  We then check the two match before actually executing
the command.

The FC transport driver already had such a field, which is removed in
favour of the common one.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>nvme: remove handling of multiple AEN requests</title>
<updated>2017-11-11T02:53:25Z</updated>
<author>
<name>Keith Busch</name>
</author>
<published>2017-11-07T22:13:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ad22c355b707a8d8d48e282aadc01c0b0604b2e9'/>
<id>urn:sha1:ad22c355b707a8d8d48e282aadc01c0b0604b2e9</id>
<content type='text'>
The driver can handle tracking only one AEN request, so this patch
removes handling for multiple ones.

Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: James Smart  &lt;james.smart@broadcom.com&gt;
Signed-off-by: Keith Busch &lt;keith.busch@intel.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>nvme: centralize AEN defines</title>
<updated>2017-11-11T02:53:25Z</updated>
<author>
<name>Keith Busch</name>
</author>
<published>2017-11-07T22:13:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=38dabe210fbab4e7e8a03670ab3ba42f247ea08f'/>
<id>urn:sha1:38dabe210fbab4e7e8a03670ab3ba42f247ea08f</id>
<content type='text'>
All the transports were unnecessarilly duplicating the AEN request
accounting. This patch defines everything in one place.

Signed-off-by: Keith Busch &lt;keith.busch@intel.com&gt;
Reviewed-by: Guan Junxiong &lt;guanjunxiong@huawei.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>nvme: consolidate common code from -&gt;reset_work</title>
<updated>2017-11-01T15:28:06Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2017-10-29T08:44:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6cd53d14aaa006b5543f06fbf5e1680ce61c6c6e'/>
<id>urn:sha1:6cd53d14aaa006b5543f06fbf5e1680ce61c6c6e</id>
<content type='text'>
No change in behavior except that the FC code cancels two work items a
little later now.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: James Smart &lt;james.smart@broadcom.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvme: move controller deletion to common code</title>
<updated>2017-11-01T15:28:04Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2017-10-29T08:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c5017e85705bfea721732e153305d1988ff965c2'/>
<id>urn:sha1:c5017e85705bfea721732e153305d1988ff965c2</id>
<content type='text'>
Move the -&gt;delete_work and the associated helpers to common code instead
of duplicating them in every driver.  This also adds the missing reference
get/put for the loop driver.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: James Smart &lt;james.smart@broadcom.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvme: switch controller refcounting to use struct device</title>
<updated>2017-10-27T06:04:07Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2017-10-18T11:25:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d22524a4782a943bb02a9cf6885ac470210aabfc'/>
<id>urn:sha1:d22524a4782a943bb02a9cf6885ac470210aabfc</id>
<content type='text'>
Instead of allocating a separate struct device for the character device
handle embedd it into struct nvme_ctrl and use it for the main controller
refcounting.  This removes double refcounting and gets us an automatic
reference for the character device operations.  We keep ctrl-&gt;device as a
pointer for now to avoid chaning printks all over, but in the future we
could look into message printing helpers that take a controller structure
similar to what other subsystems do.

Note the delete_ctrl operation always already has a reference (either
through sysfs due this change, or because every open file on the
/dev/nvme-fabrics node has a refernece) when it is entered now, so we
don't need to do the unless_zero variant there.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Hannes Reinecke &lt;hare@suse.com&gt;
</content>
</entry>
<entry>
<title>nvme-loop: Add BLK_MQ_F_NO_SCHED flag to admin tag set</title>
<updated>2017-10-19T08:58:54Z</updated>
<author>
<name>Israel Rukshin</name>
</author>
<published>2017-10-18T12:38:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=86f36b9c6c6cda28c86ead09323f55018e5e64df'/>
<id>urn:sha1:86f36b9c6c6cda28c86ead09323f55018e5e64df</id>
<content type='text'>
This flag is useful for admin queues that aren't used for normal IO.

Signed-off-by: Israel Rukshin &lt;israelr@mellanox.com&gt;
Reviewed-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: Max Gurtovoy &lt;maxg@mellanox.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvme: Add admin_tagset pointer to nvme_ctrl</title>
<updated>2017-08-28T19:38:24Z</updated>
<author>
<name>Sagi Grimberg</name>
</author>
<published>2017-07-10T06:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=34b6c2315eb66e6411261aa440f6e3c4cded3506'/>
<id>urn:sha1:34b6c2315eb66e6411261aa440f6e3c4cded3506</id>
<content type='text'>
Will be used when we centralize control flows.

Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
</feed>
