public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail.com>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org
Cc: james.smart@broadcom.com, kbusch@kernel.org, hch@lst.de,
	sagi@grimberg.me
Subject: Re: [PATCH 2/2] nvme-fc: move common code into helper
Date: Fri, 2 Dec 2022 08:09:29 -0800	[thread overview]
Message-ID: <f1f9041d-90d4-c483-84cb-d2c48e544c82@gmail.com> (raw)
In-Reply-To: <20221130213341.9625-2-kch@nvidia.com>

On 11/30/2022 1:33 PM, Chaitanya Kulkarni wrote:
> Add a helper to move the duplicate code for error message
> from nvme_fc_rcv_ls_req() to nvme_fc_rcv_ls_req_err_msg().
> 
> Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
> ---
>   drivers/nvme/host/fc.c | 19 +++++++++++--------
>   1 file changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
> index 06bae7150087..42fa450187f8 100644
> --- a/drivers/nvme/host/fc.c
> +++ b/drivers/nvme/host/fc.c
> @@ -1701,6 +1701,15 @@ nvme_fc_handle_ls_rqst_work(struct work_struct *work)
>   	spin_unlock_irqrestore(&rport->lock, flags);
>   }
>   
> +static
> +void nvme_fc_rcv_ls_req_err_msg(struct nvme_fc_lport *lport,
> +				struct fcnvme_ls_rqst_w0 *w0)
> +{
> +	dev_info(lport->dev, "RCV %s LS failed: No memory\n",
> +		(w0->ls_cmd <= NVME_FC_LAST_LS_CMD_VALUE) ?
> +			nvmefc_ls_names[w0->ls_cmd] : "");
> +}
> +
>   /**
>    * nvme_fc_rcv_ls_req - transport entry point called by an LLDD
>    *                       upon the reception of a NVME LS request.
> @@ -1755,10 +1764,7 @@ nvme_fc_rcv_ls_req(struct nvme_fc_remote_port *portptr,
>   
>   	lsop = kzalloc(sizeof(*lsop), GFP_KERNEL);
>   	if (!lsop) {
> -		dev_info(lport->dev,
> -			"RCV %s LS failed: No memory\n",
> -			(w0->ls_cmd <= NVME_FC_LAST_LS_CMD_VALUE) ?
> -				nvmefc_ls_names[w0->ls_cmd] : "");
> +		nvme_fc_rcv_ls_req_err_msg(lport, w0);
>   		ret = -ENOMEM;
>   		goto out_put;
>   	}
> @@ -1766,10 +1772,7 @@ nvme_fc_rcv_ls_req(struct nvme_fc_remote_port *portptr,
>   	lsop->rqstbuf = kzalloc(sizeof(*lsop->rqstbuf), GFP_KERNEL);
>   	lsop->rspbuf = kzalloc(sizeof(*lsop->rspbuf), GFP_KERNEL);
>   	if (!lsop->rqstbuf || !lsop->rspbuf) {
> -		dev_info(lport->dev,
> -			"RCV %s LS failed: No memory\n",
> -			(w0->ls_cmd <= NVME_FC_LAST_LS_CMD_VALUE) ?
> -				nvmefc_ls_names[w0->ls_cmd] : "");
> +		nvme_fc_rcv_ls_req_err_msg(lport, w0);
>   		ret = -ENOMEM;
>   		goto out_free;
>   	}

OK

Reviewed-by: James Smart <jsmart2021@gmail.com>

-- james




  reply	other threads:[~2022-12-02 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 21:33 [PATCH 1/2] nvme-fc: avoid null pointer dereference Chaitanya Kulkarni
2022-11-30 21:33 ` [PATCH 2/2] nvme-fc: move common code into helper Chaitanya Kulkarni
2022-12-02 16:09   ` James Smart [this message]
2022-12-02 16:07 ` [PATCH 1/2] nvme-fc: avoid null pointer dereference James Smart
2022-12-06  8:08 ` 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=f1f9041d-90d4-c483-84cb-d2c48e544c82@gmail.com \
    --to=jsmart2021@gmail.com \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --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