<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/nvme/target/fc.c, branch linux-6.5.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.5.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.5.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2023-02-01T13:18:46Z</updated>
<entry>
<title>nvme-fc: fix a missing queue put in nvmet_fc_ls_create_association</title>
<updated>2023-02-01T13:18:46Z</updated>
<author>
<name>Amit Engel</name>
</author>
<published>2023-01-23T12:37:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0cab4404874f2de52617de8400c844891c6ea1ce'/>
<id>urn:sha1:0cab4404874f2de52617de8400c844891c6ea1ce</id>
<content type='text'>
As part of nvmet_fc_ls_create_association there is a case where
nvmet_fc_alloc_target_queue fails right after a new association with an
admin queue is created. In this case, no one releases the get taken in
nvmet_fc_alloc_target_assoc.  This fix is adding the missing put.

Signed-off-by: Amit Engel &lt;Amit.Engel@dell.com&gt;
Reviewed-by: James Smart &lt;jsmart2021@gmail.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet: use a private workqueue instead of the system workqueue</title>
<updated>2022-03-29T07:29:04Z</updated>
<author>
<name>Sagi Grimberg</name>
</author>
<published>2022-03-21T11:57:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8832cf922151e9dfa2821736beb0ae2dd3968b6e'/>
<id>urn:sha1:8832cf922151e9dfa2821736beb0ae2dd3968b6e</id>
<content type='text'>
Any attempt to flush kernel-global WQs has possibility of deadlock
so we should simply stop using them, instead introduce nvmet_wq
which is the generic nvmet workqueue for work elements that
don't explicitly require a dedicated workqueue (by the mere fact
that they are using the system_wq).

Changes were done using the following replaces:

 - s/schedule_work(/queue_work(nvmet_wq, /g
 - s/schedule_delayed_work(/queue_delayed_work(nvmet_wq, /g
 - s/flush_scheduled_work()/flush_workqueue(nvmet_wq)/g

Reported-by: Tetsuo Handa &lt;penguin-kernel@I-love.SAKURA.ne.jp&gt;
Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: Chaitanya Kulkarni &lt;kch@nvidia.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: fix kernel-doc warning for nvmet_fc_unregister_targetport</title>
<updated>2022-03-14T07:43:06Z</updated>
<author>
<name>Chaitanya Kulkarni</name>
</author>
<published>2022-03-09T05:59:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0acb8231ebae5175260a7da853f525f2730cc095'/>
<id>urn:sha1:0acb8231ebae5175260a7da853f525f2730cc095</id>
<content type='text'>
This fixes following kernel-doc warning:-

drivers/nvme/target/fc.c:1619: warning: expecting prototype for nvme_fc_unregister_targetport(). Prototype was for nvmet_fc_unregister_targetport() instead

Signed-off-by: Chaitanya Kulkarni &lt;kch@nvidia.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: fix kernel-doc warning for nvmet_fc_register_targetport</title>
<updated>2022-03-14T07:43:06Z</updated>
<author>
<name>Chaitanya Kulkarni</name>
</author>
<published>2022-03-09T05:59:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b2fb99e42598ba5d1ac045fb39a2b38fd80dd8d2'/>
<id>urn:sha1:b2fb99e42598ba5d1ac045fb39a2b38fd80dd8d2</id>
<content type='text'>
This fixes following kernel-doc warning :-

drivers/nvme/target/fc.c:1365: warning: expecting prototype for nvme_fc_register_targetport(). Prototype was for nvmet_fc_register_targetport() instead

Signed-off-by: Chaitanya Kulkarni &lt;kch@nvidia.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: replace ida_simple[get|remove] with the simler ida_[alloc|free]</title>
<updated>2022-02-28T11:45:05Z</updated>
<author>
<name>Sagi Grimberg</name>
</author>
<published>2022-02-14T09:07:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6dd0f465d57c4522294d0fd42fde7603264d0871'/>
<id>urn:sha1:6dd0f465d57c4522294d0fd42fde7603264d0871</id>
<content type='text'>
ida_simple_[get|remove] are wrappers anyways.

Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: Keith Busch &lt;kbusch@kernel.org&gt;
Reviewed-by: Chaitanya Kulkarni &lt;kch@nvidia.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: do not check for invalid target port in nvmet_fc_handle_fcp_rqst()</title>
<updated>2021-06-17T13:51:19Z</updated>
<author>
<name>Hannes Reinecke</name>
</author>
<published>2021-05-25T12:54:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2a4a910aa4f0acc428dc8d10227c42e14ed21d10'/>
<id>urn:sha1:2a4a910aa4f0acc428dc8d10227c42e14ed21d10</id>
<content type='text'>
When parsing a request in nvmet_fc_handle_fcp_rqst() we should not
check for invalid target ports; if we do the command is aborted
from the fcp layer, causing the host to assume a transport error.
Rather we should still forward this request to the nvmet layer, which
will then correctly fail the command with an appropriate error status.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Reviewed-by: James Smart &lt;jsmart2021@gmail.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: simplify nvmet_fc_alloc_hostport</title>
<updated>2021-04-15T06:12:53Z</updated>
<author>
<name>Amit Engel</name>
</author>
<published>2021-03-22T19:57:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0d8ddeea11d00010c8b0ecbe9d3b90811cd19867'/>
<id>urn:sha1:0d8ddeea11d00010c8b0ecbe9d3b90811cd19867</id>
<content type='text'>
Once a host is already created, avoid allocate additional hostports that
will be thrown away. add an helper function to handle host search.

Reviewed-by: Himanshu Madhani &lt;himanshu.madhani@oracle.com&gt;
Signed-off-by: James Smart &lt;jsmart2021@gmail.com&gt;
Signed-off-by: Amit Engel &lt;amit.engel@dell.com&gt;
Reviewed-by: Chaitanya Kulkarni &lt;chaitanya.kulkarni@wdc.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: update function documentation</title>
<updated>2021-04-02T16:48:27Z</updated>
<author>
<name>Chaitanya Kulkarni</name>
</author>
<published>2021-03-01T02:06:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b53d47418d98dbf5cd082e756a9e4e2a426492d7'/>
<id>urn:sha1:b53d47418d98dbf5cd082e756a9e4e2a426492d7</id>
<content type='text'>
Add minimum description of the hosthandle parameter for
nvmet_fc_rcv_ls_req() so that we can get rid of the following warning.

drivers/nvme//target/fc.c:2009: warning: Function parameter or member 'hosthandle' not described in 'nvmet_fc_rcv_ls_req

Signed-off-by: Chaitanya Kulkarni &lt;chaitanya.kulkarni@wdc.com&gt;
Reviewed-by: James Smart &lt;jsmart2021@gmail.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: add a missing __rcu annotation to nvmet_fc_tgt_assoc.queues</title>
<updated>2021-02-10T15:38:04Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2021-02-07T16:17:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b5df8e79a293739f031f25eb45de350165033ea4'/>
<id>urn:sha1:b5df8e79a293739f031f25eb45de350165033ea4</id>
<content type='text'>
Make sparse happy after the recent conversion to RCU lookups.

Fixes: 4e2f02bf77da ("nvmet-fc: use RCU proctection for assoc_list")
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;
Reviewed-by: Chaitanya Kulkarni &lt;chaitanya.kulkarni@wdc.com&gt;
Reviewed-by: James Smart &lt;james.smart@broadcom.com&gt;
</content>
</entry>
<entry>
<title>nvmet-fc: use RCU proctection for assoc_list</title>
<updated>2021-02-02T09:26:10Z</updated>
<author>
<name>Leonid Ravich</name>
</author>
<published>2021-01-03T18:12:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4e2f02bf77dac7b8c841f93ae5a71556d733cb04'/>
<id>urn:sha1:4e2f02bf77dac7b8c841f93ae5a71556d733cb04</id>
<content type='text'>
searching assoc_list protected by rcu_read_lock if list not changed inline.
and according to the rcu list rules.

queue array embedded into nvmet_fc_tgt_assoc protected by rcu_read_lock
according to rcu dereference/assign rules.

queue and assoc object freed after grace period by call_rcu.

tgtport lock taken for changing assoc_list.

Reviewed-by: Eldad Zinger &lt;Eldad.Zinger@dell.com&gt;
Reviewed-by: Elad Grupi &lt;Elad.Grupi@dell.com&gt;
Reviewed-by: James Smart &lt;james.smart@broadcom.com&gt;
Signed-off-by: Leonid Ravich &lt;Leonid.Ravich@emc.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
</feed>
