From: John Garry <john.g.garry@oracle.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.d, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, darren.kenny@oracle.com
Subject: Re: [PATCH] nvme: Fix incorrect cdw15 value in passthru error logging
Date: Tue, 17 Jun 2025 07:26:40 +0100 [thread overview]
Message-ID: <7a4d3674-53b9-4f9c-92e0-74aa1202f500@oracle.com> (raw)
In-Reply-To: <20250616181936.2094176-1-alok.a.tiwari@oracle.com>
On 16/06/2025 19:19, Alok Tiwari wrote:
> Fix an error in nvme_log_err_passthru() where cdw14 was incorrectly
> printed twice instead of cdw15. This fix ensures accurate logging of
> the full passthrough command payload.
>
> Fixes: 9f079dda1433 ("nvme: allow passthru cmd error logging")
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
> Is it ok to keep Fixes tag for this fix?
> ---
> drivers/nvme/host/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 92697f98c601..f3e07cb92385 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -386,7 +386,7 @@ static void nvme_log_err_passthru(struct request *req)
> nr->cmd->common.cdw12,
> nr->cmd->common.cdw13,
> nr->cmd->common.cdw14,
> - nr->cmd->common.cdw14);
> + nr->cmd->common.cdw15);
Apart from the fix, any reason not to use le32_to_cpu() when getting
these values? AFAICS, they are __le32 type
> }
>
> enum nvme_disposition {
prev parent reply other threads:[~2025-06-17 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 18:19 Alok Tiwari
2025-06-16 22:04 ` Martin K. Petersen
2025-06-17 6:26 ` John Garry [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=7a4d3674-53b9-4f9c-92e0-74aa1202f500@oracle.com \
--to=john.g.garry@oracle.com \
--cc=alok.a.tiwari@oracle.com \
--cc=axboe@kernel.dk \
--cc=darren.kenny@oracle.com \
--cc=hch@lst.d \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®