linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: himanshu.madhani@oracle.com
To: James Smart <jsmart2021@gmail.com>, linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
	stable@vger.kernel.org
Subject: Re: [PATCH] nvme-fc: Revert - add module to ops template to allow module references
Date: Fri, 3 Apr 2020 11:38:50 -0500	[thread overview]
Message-ID: <6ad66e15-4815-146a-9921-c776559e3c75@oracle.com> (raw)
In-Reply-To: <20200403143320.49522-1-jsmart2021@gmail.com>


On 4/3/20 9:33 AM, James Smart wrote:
> This patch reverts the commit for
>     nvme_fc: add module to ops template to allow module references
>
> The original patch was to resolve the lldd being able to be unloaded
> while being used to talk to the boot device of the system. However, the
> end result of the original patch is that any driver unload while a nvme
> controller is live via the lldd is now being prohibited. Given the module
> reference, the module teardown routine can't be called, thus there's no
> way, other than manual actions to terminate the controllers.
>
> -- james
>
> Fixes: 863fbae929c7 ("nvme_fc: add module to ops template to allow module  references")
> Cc: <stable@vger.kernel.org> # v5.4+
> Signed-off-by: James Smart <jsmart2021@gmail.com>
> Cc: Himanshu Madhani <himanshu.madhani@oracle.com>
> CC: Christoph Hellwig <hch@lst.de>
> CC: Keith Busch <kbusch@kernel.org>
> ---
>   drivers/nvme/host/fc.c          | 14 ++------------
>   drivers/nvme/target/fcloop.c    |  1 -
>   drivers/scsi/lpfc/lpfc_nvme.c   |  2 --
>   drivers/scsi/qla2xxx/qla_nvme.c |  1 -
>   include/linux/nvme-fc-driver.h  |  4 ----
>   5 files changed, 2 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
> index a8bf2fb1287b..7dfc4a2ecf1e 100644
> --- a/drivers/nvme/host/fc.c
> +++ b/drivers/nvme/host/fc.c
> @@ -342,8 +342,7 @@ nvme_fc_register_localport(struct nvme_fc_port_info *pinfo,
>   	    !template->ls_req || !template->fcp_io ||
>   	    !template->ls_abort || !template->fcp_abort ||
>   	    !template->max_hw_queues || !template->max_sgl_segments ||
> -	    !template->max_dif_sgl_segments || !template->dma_boundary ||
> -	    !template->module) {
> +	    !template->max_dif_sgl_segments || !template->dma_boundary) {
>   		ret = -EINVAL;
>   		goto out_reghost_failed;
>   	}
> @@ -2016,7 +2015,6 @@ nvme_fc_ctrl_free(struct kref *ref)
>   {
>   	struct nvme_fc_ctrl *ctrl =
>   		container_of(ref, struct nvme_fc_ctrl, ref);
> -	struct nvme_fc_lport *lport = ctrl->lport;
>   	unsigned long flags;
>   
>   	if (ctrl->ctrl.tagset) {
> @@ -2043,7 +2041,6 @@ nvme_fc_ctrl_free(struct kref *ref)
>   	if (ctrl->ctrl.opts)
>   		nvmf_free_options(ctrl->ctrl.opts);
>   	kfree(ctrl);
> -	module_put(lport->ops->module);
>   }
>   
>   static void
> @@ -3074,15 +3071,10 @@ nvme_fc_init_ctrl(struct device *dev, struct nvmf_ctrl_options *opts,
>   		goto out_fail;
>   	}
>   
> -	if (!try_module_get(lport->ops->module)) {
> -		ret = -EUNATCH;
> -		goto out_free_ctrl;
> -	}
> -
>   	idx = ida_simple_get(&nvme_fc_ctrl_cnt, 0, 0, GFP_KERNEL);
>   	if (idx < 0) {
>   		ret = -ENOSPC;
> -		goto out_mod_put;
> +		goto out_free_ctrl;
>   	}
>   
>   	ctrl->ctrl.opts = opts;
> @@ -3232,8 +3224,6 @@ nvme_fc_init_ctrl(struct device *dev, struct nvmf_ctrl_options *opts,
>   out_free_ida:
>   	put_device(ctrl->dev);
>   	ida_simple_remove(&nvme_fc_ctrl_cnt, ctrl->cnum);
> -out_mod_put:
> -	module_put(lport->ops->module);
>   out_free_ctrl:
>   	kfree(ctrl);
>   out_fail:
> diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c
> index 9861fcea39f6..f69ce66e2d44 100644
> --- a/drivers/nvme/target/fcloop.c
> +++ b/drivers/nvme/target/fcloop.c
> @@ -875,7 +875,6 @@ fcloop_targetport_delete(struct nvmet_fc_target_port *targetport)
>   #define FCLOOP_DMABOUND_4G		0xFFFFFFFF
>   
>   static struct nvme_fc_port_template fctemplate = {
> -	.module			= THIS_MODULE,
>   	.localport_delete	= fcloop_localport_delete,
>   	.remoteport_delete	= fcloop_remoteport_delete,
>   	.create_queue		= fcloop_create_queue,
> diff --git a/drivers/scsi/lpfc/lpfc_nvme.c b/drivers/scsi/lpfc/lpfc_nvme.c
> index f6c8963c915d..db4a04a207ec 100644
> --- a/drivers/scsi/lpfc/lpfc_nvme.c
> +++ b/drivers/scsi/lpfc/lpfc_nvme.c
> @@ -1985,8 +1985,6 @@ lpfc_nvme_fcp_abort(struct nvme_fc_local_port *pnvme_lport,
>   
>   /* Declare and initialization an instance of the FC NVME template. */
>   static struct nvme_fc_port_template lpfc_nvme_template = {
> -	.module	= THIS_MODULE,
> -
>   	/* initiator-based functions */
>   	.localport_delete  = lpfc_nvme_localport_delete,
>   	.remoteport_delete = lpfc_nvme_remoteport_delete,
> diff --git a/drivers/scsi/qla2xxx/qla_nvme.c b/drivers/scsi/qla2xxx/qla_nvme.c
> index bfcd02fdf2b8..941aa53363f5 100644
> --- a/drivers/scsi/qla2xxx/qla_nvme.c
> +++ b/drivers/scsi/qla2xxx/qla_nvme.c
> @@ -610,7 +610,6 @@ static void qla_nvme_remoteport_delete(struct nvme_fc_remote_port *rport)
>   }
>   
>   static struct nvme_fc_port_template qla_nvme_fc_transport = {
> -	.module	= THIS_MODULE,
>   	.localport_delete = qla_nvme_localport_delete,
>   	.remoteport_delete = qla_nvme_remoteport_delete,
>   	.create_queue   = qla_nvme_alloc_queue,
> diff --git a/include/linux/nvme-fc-driver.h b/include/linux/nvme-fc-driver.h
> index 6d0d70f3219c..10f81629b9ce 100644
> --- a/include/linux/nvme-fc-driver.h
> +++ b/include/linux/nvme-fc-driver.h
> @@ -270,8 +270,6 @@ struct nvme_fc_remote_port {
>    *
>    * Host/Initiator Transport Entrypoints/Parameters:
>    *
> - * @module:  The LLDD module using the interface
> - *
>    * @localport_delete:  The LLDD initiates deletion of a localport via
>    *       nvme_fc_deregister_localport(). However, the teardown is
>    *       asynchronous. This routine is called upon the completion of the
> @@ -385,8 +383,6 @@ struct nvme_fc_remote_port {
>    *       Value is Mandatory. Allowed to be zero.
>    */
>   struct nvme_fc_port_template {
> -	struct module	*module;
> -
>   	/* initiator-based functions */
>   	void	(*localport_delete)(struct nvme_fc_local_port *);
>   	void	(*remoteport_delete)(struct nvme_fc_remote_port *);
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-04-03 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 14:33 [PATCH] nvme-fc: Revert - add module to ops template to allow module references James Smart
2020-04-03 16:38 ` himanshu.madhani [this message]
2020-04-04  7:10 ` 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=6ad66e15-4815-146a-9921-c776559e3c75@oracle.com \
    --to=himanshu.madhani@oracle.com \
    --cc=hch@lst.de \
    --cc=jsmart2021@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    /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).