All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Leng <lengchao@huawei.com>
To: Keith Busch <kbusch@fb.com>, <linux-nvme@lists.infradead.org>,
	<hch@lst.de>, <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>, Jeff Lien <jeff.lien@wdc.com>
Subject: Re: [PATCH] nvme: copy firmware_rev on each init
Date: Wed, 21 Sep 2022 09:48:33 +0800	[thread overview]
Message-ID: <50851cfd-ae9b-290d-1d27-942682840e79@huawei.com> (raw)
In-Reply-To: <20220919194508.1704346-1-kbusch@fb.com>



On 2022/9/20 3:45, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> The firmware revision can change on after a reset so copy the most
> recent info each time instead of just the first time, otherwise the
> sysfs firmware_rev entry may contain stale data.
> 
> Reported-by: Jeff Lien <jeff.lien@wdc.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
>   drivers/nvme/host/core.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index ea6694fd550f..e56ecc7fda2d 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -2893,7 +2893,6 @@ static int nvme_init_subsystem(struct nvme_ctrl *ctrl, struct nvme_id_ctrl *id)
>   	nvme_init_subnqn(subsys, ctrl, id);
>   	memcpy(subsys->serial, id->sn, sizeof(subsys->serial));
>   	memcpy(subsys->model, id->mn, sizeof(subsys->model));
> -	memcpy(subsys->firmware_rev, id->fr, sizeof(subsys->firmware_rev));
>   	subsys->vendor_id = le16_to_cpu(id->vid);
>   	subsys->cmic = id->cmic;
>   
> @@ -3112,6 +3111,8 @@ static int nvme_init_identify(struct nvme_ctrl *ctrl)
>   				ctrl->quirks |= core_quirks[i].quirks;
>   		}
>   	}
> +	memcpy(ctrl->subsys->firmware_rev, id->fr,
> +	       sizeof(ctrl->subsys->firmware_rev));
Perhaps it would be better to place it near the call to nvme_init_subsystem.
>   
>   	if (force_apst && (ctrl->quirks & NVME_QUIRK_NO_DEEPEST_PS)) {
>   		dev_warn(ctrl->device, "forcibly allowing all power states due to nvme_core.force_apst -- use at your own risk\n");
> 
Anyway, looks good to me.

Reviewed-by: Chao Leng <lengchao@huawei.com>


      parent reply	other threads:[~2022-09-21  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 19:45 [PATCH] nvme: copy firmware_rev on each init Keith Busch
2022-09-19 23:04 ` Chaitanya Kulkarni
2022-09-20  8:23 ` Sagi Grimberg
2022-09-21  1:48 ` Chao Leng [this message]

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=50851cfd-ae9b-290d-1d27-942682840e79@huawei.com \
    --to=lengchao@huawei.com \
    --cc=hch@lst.de \
    --cc=jeff.lien@wdc.com \
    --cc=kbusch@fb.com \
    --cc=kbusch@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.