From: Klaus Jensen <its@irrelevant.dk>
To: Ankit Kumar <ankit.kumar@samsung.com>
Cc: kbusch@kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] hw/nvme: fix CRC64 for guard tag
Date: Tue, 8 Aug 2023 07:58:14 +0200 [thread overview]
Message-ID: <ZNHZdoYnoFegAyRj@cormorant.local> (raw)
In-Reply-To: <20230807212745.70151-2-ankit.kumar@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Aug 8 02:57, Ankit Kumar wrote:
> The nvme CRC64 generator expects the caller to pass inverted seed value.
> Pass inverted crc value for metadata buffer.
>
> Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
> ---
> hw/nvme/dif.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/nvme/dif.c b/hw/nvme/dif.c
> index 63c44c86ab..01b19c3373 100644
> --- a/hw/nvme/dif.c
> +++ b/hw/nvme/dif.c
> @@ -115,7 +115,7 @@ static void nvme_dif_pract_generate_dif_crc64(NvmeNamespace *ns, uint8_t *buf,
> uint64_t crc = crc64_nvme(~0ULL, buf, ns->lbasz);
>
> if (pil) {
> - crc = crc64_nvme(crc, mbuf, pil);
> + crc = crc64_nvme(~crc, mbuf, pil);
> }
>
> dif->g64.guard = cpu_to_be64(crc);
> @@ -246,7 +246,7 @@ static uint16_t nvme_dif_prchk_crc64(NvmeNamespace *ns, NvmeDifTuple *dif,
> uint64_t crc = crc64_nvme(~0ULL, buf, ns->lbasz);
>
> if (pil) {
> - crc = crc64_nvme(crc, mbuf, pil);
> + crc = crc64_nvme(~crc, mbuf, pil);
> }
>
> trace_pci_nvme_dif_prchk_guard_crc64(be64_to_cpu(dif->g64.guard), crc);
> --
> 2.25.1
>
Good catch, thanks!
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-08 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230807160836epcas5p34398954fecd7388469012404b09b78f9@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Ankit Kumar
2023-08-07 21:27 ` [PATCH 1/3] hw/nvme: fix CRC64 for guard tag Ankit Kumar
2023-08-08 5:58 ` Klaus Jensen [this message]
2023-08-07 21:27 ` [PATCH 2/3] hw/nvme: fix disable pi checks for Type 3 protection Ankit Kumar
2023-08-08 5:57 ` Klaus Jensen
2023-08-07 21:27 ` [PATCH 3/3] docs: update hw/nvme documentation for protection information Ankit Kumar
2023-08-08 5:59 ` Klaus Jensen
2023-08-08 6:04 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Michael Tokarev
2023-08-08 6:06 ` Klaus Jensen
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=ZNHZdoYnoFegAyRj@cormorant.local \
--to=its@irrelevant.dk \
--cc=ankit.kumar@samsung.com \
--cc=kbusch@kernel.org \
--cc=qemu-devel@nongnu.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 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.