From: "Rafał Miłecki" <rafal@milecki.pl>
To: INAGAKI Hiroshi <musashino.open@gmail.com>,
srinivas.kandagatla@linaro.org
Cc: chunkeey@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] nvmem: u-boot-env: align endianness of crc32 values
Date: Mon, 20 Feb 2023 09:01:36 +0100 [thread overview]
Message-ID: <724bcb6f-775d-a7be-d47c-447dc8ac4c19@milecki.pl> (raw)
In-Reply-To: <20230213132351.837-1-musashino.open@gmail.com>
On 13.02.2023 14:23, INAGAKI Hiroshi wrote:
> @@ -117,8 +117,8 @@ static int u_boot_env_parse(struct u_boot_env *priv)
> size_t crc32_offset;
> size_t data_offset;
> size_t data_len;
> - uint32_t crc32;
> - uint32_t calc;
> + __le32 crc32;
> + __le32 calc;
> size_t bytes;
> uint8_t *buf;
> int err;
> @@ -152,11 +152,11 @@ static int u_boot_env_parse(struct u_boot_env *priv)
> data_offset = offsetof(struct u_boot_env_image_broadcom, data);
> break;
> }
> - crc32 = le32_to_cpu(*(__le32 *)(buf + crc32_offset));
> + crc32 = cpu_to_le32(*(uint32_t *)(buf + crc32_offset));
> crc32_data_len = priv->mtd->size - crc32_data_offset;
> data_len = priv->mtd->size - data_offset;
>
> - calc = crc32(~0, buf + crc32_data_offset, crc32_data_len) ^ ~0L;
> + calc = cpu_to_le32(crc32(~0, buf + crc32_data_offset, crc32_data_len) ^ ~0L);
Can you see what happens on BE device if instead of this whole patch you
just replace crc32() in above line with crc32_le()?
> if (calc != crc32) {
> dev_err(dev, "Invalid calculated CRC32: 0x%08x (expected: 0x%08x)\n", calc, crc32);
> err = -EINVAL;
next prev parent reply other threads:[~2023-02-20 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 13:23 INAGAKI Hiroshi
2023-02-13 13:37 ` Rafał Miłecki
2023-02-17 17:30 ` Christian Lamparter
2023-02-19 4:45 ` INAGAKI Hiroshi
2023-02-19 12:30 ` Christian Lamparter
2023-02-20 8:01 ` Rafał Miłecki [this message]
2023-02-20 13:34 ` INAGAKI Hiroshi
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=724bcb6f-775d-a7be-d47c-447dc8ac4c19@milecki.pl \
--to=rafal@milecki.pl \
--cc=chunkeey@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=musashino.open@gmail.com \
--cc=srinivas.kandagatla@linaro.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
Powered by JetHome