nvme-fcloop: fix port deletes and callbacks
authorJames Smart <jsmart2021@gmail.com>
Tue, 19 Sep 2017 21:01:50 +0000 (14:01 -0700)
committerJens Axboe <axboe@kernel.dk>
Mon, 25 Sep 2017 18:42:11 +0000 (12:42 -0600)
commitfddc9923c6d41de9fe7b1f323a3cece53e046c88
tree2eb7c2776d6779e8f98e66144a0a3040bbf43187
parent6b71f9e1e849f82abb4a8d54ce7f4b1c71f19ac4
nvme-fcloop: fix port deletes and callbacks

Now that there are potentially long delays between when a remoteport or
targetport delete calls is made and when the callback occurs (dev_loss_tmo
timeout), no longer block in the delete routines and move the final nport
puts to the callbacks.

Moved the fcloop_nport_get/put/free routines to avoid forward declarations.

Ensure port_info structs used in registrations are nulled in case fields
are not set (ex: devloss_tmo values).

Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
drivers/nvme/target/fcloop.c