From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Xichao Zhao <zhao.xichao@vivo.com>,
Richard Weinberger <richard@nod.at>,
"open list:UBI FILE SYSTEM (UBIFS)"
<linux-mtd@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] ubifs: Simplify the code using ubifs_crc_node
Date: Tue, 12 Aug 2025 11:06:33 +0800 [thread overview]
Message-ID: <b0c99eb4-ff3d-cfa9-5f4d-92d138e688a7@huawei.com> (raw)
In-Reply-To: <20250812021009.414756-3-zhao.xichao@vivo.com>
在 2025/8/12 10:10, Xichao Zhao 写道:
> Replace part of the code using ubifs_crc_node.
>
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
> ---
> fs/ubifs/io.c | 9 ++-------
> fs/ubifs/recovery.c | 4 +---
> 2 files changed, 3 insertions(+), 10 deletions(-)
>
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/fs/ubifs/io.c b/fs/ubifs/io.c
> index e0dfe6827d65..6c6d68242779 100644
> --- a/fs/ubifs/io.c
> +++ b/fs/ubifs/io.c
> @@ -327,8 +327,6 @@ int ubifs_check_node(const struct ubifs_info *c, const void *buf, int len,
> */
> void ubifs_pad(const struct ubifs_info *c, void *buf, int pad)
> {
> - uint32_t crc;
> -
> ubifs_assert(c, pad >= 0);
>
> if (pad >= UBIFS_PAD_NODE_SZ) {
> @@ -343,8 +341,7 @@ void ubifs_pad(const struct ubifs_info *c, void *buf, int pad)
> ch->len = cpu_to_le32(UBIFS_PAD_NODE_SZ);
> pad -= UBIFS_PAD_NODE_SZ;
> pad_node->pad_len = cpu_to_le32(pad);
> - crc = crc32(UBIFS_CRC32_INIT, buf + 8, UBIFS_PAD_NODE_SZ - 8);
> - ch->crc = cpu_to_le32(crc);
> + ubifs_crc_node(buf, UBIFS_PAD_NODE_SZ);
> memset(buf + UBIFS_PAD_NODE_SZ, 0, pad);
> } else if (pad > 0)
> /* Too little space, padding node won't fit */
> @@ -469,7 +466,6 @@ void ubifs_prepare_node(struct ubifs_info *c, void *node, int len, int pad)
> */
> void ubifs_prep_grp_node(struct ubifs_info *c, void *node, int len, int last)
> {
> - uint32_t crc;
> struct ubifs_ch *ch = node;
> unsigned long long sqnum = next_sqnum(c);
>
> @@ -483,8 +479,7 @@ void ubifs_prep_grp_node(struct ubifs_info *c, void *node, int len, int last)
> ch->group_type = UBIFS_IN_NODE_GROUP;
> ch->sqnum = cpu_to_le64(sqnum);
> ch->padding[0] = ch->padding[1] = 0;
> - crc = crc32(UBIFS_CRC32_INIT, node + 8, len - 8);
> - ch->crc = cpu_to_le32(crc);
> + ubifs_crc_node(node, len);
> }
>
> /**
> diff --git a/fs/ubifs/recovery.c b/fs/ubifs/recovery.c
> index f0d51dd21c9e..b36dc9b032f4 100644
> --- a/fs/ubifs/recovery.c
> +++ b/fs/ubifs/recovery.c
> @@ -1406,7 +1406,6 @@ static int fix_size_in_place(struct ubifs_info *c, struct size_entry *e)
> union ubifs_key key;
> int err, lnum, offs, len;
> loff_t i_size;
> - uint32_t crc;
>
> /* Locate the inode node LEB number and offset */
> ino_key_init(c, &key, e->inum);
> @@ -1428,8 +1427,7 @@ static int fix_size_in_place(struct ubifs_info *c, struct size_entry *e)
> ino = c->sbuf + offs;
> ino->size = cpu_to_le64(e->d_size);
> len = le32_to_cpu(ino->ch.len);
> - crc = crc32(UBIFS_CRC32_INIT, (void *)ino + 8, len - 8);
> - ino->ch.crc = cpu_to_le32(crc);
> + ubifs_crc_node((void *)ino, len);
> /* Work out where data in the LEB ends and free space begins */
> p = c->sbuf;
> len = c->leb_size - 1;
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2025-08-12 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 2:10 [PATCH v2 0/2] ubifs: Simplify the code and remove unnecessary parameters Xichao Zhao
2025-08-12 2:10 ` [PATCH v2 1/2] ubifs: Remove unnecessary parameters '*c' Xichao Zhao
2025-08-12 3:06 ` Zhihao Cheng
2025-08-12 2:10 ` [PATCH v2 2/2] ubifs: Simplify the code using ubifs_crc_node Xichao Zhao
2025-08-12 3:06 ` Zhihao Cheng [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=b0c99eb4-ff3d-cfa9-5f4d-92d138e688a7@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=zhao.xichao@vivo.com \
/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;
as well as URLs for NNTP newsgroup(s).