linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Lihua <hucool.lihua@huawei.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	 linux-mtd <linux-mtd@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 Wei Yongjun <weiyongjun1@huawei.com>,
	 yusongping <yusongping@huawei.com>
Subject: Re: [PATCH] ubifs: Fix build errors as symbol undefined
Date: Mon, 21 Nov 2022 09:00:02 +0100 (CET)	[thread overview]
Message-ID: <540631712.260900.1669017601995.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <ed4618a5-67b4-7ee5-f172-a2709ee738fa@huawei.com>

----- Ursprüngliche Mail -----
> Von: "Lihua" <hucool.lihua@huawei.com>
> An: "richard" <richard@nod.at>
> CC: "Sascha Hauer" <s.hauer@pengutronix.de>, "linux-mtd" <linux-mtd@lists.infradead.org>, "linux-kernel"
> <linux-kernel@vger.kernel.org>, "Wei Yongjun" <weiyongjun1@huawei.com>, "yusongping" <yusongping@huawei.com>
> Gesendet: Montag, 21. November 2022 02:54:53
> Betreff: Re: [PATCH] ubifs: Fix build errors as symbol undefined

> You can verify it with the config in the attachment. TKS :D

Thanks for your .config, I was able to identify the problem.
When CONFIG_CC_OPTIMIZE_FOR_SIZE is set the compiler does not optimize this construct:

        err = ubifs_node_check_hash(c, buf, zbr->hash);
        if (err) {
                ubifs_bad_hash(c, buf, zbr->hash, lnum, offs);
                return 0;
        }

With CONFIG_UBIFS_FS_AUTHENTICATION not set, the compiler can assume that
ubifs_node_check_hash() is never true and drops the call to ubifs_bad_hash().
Is CONFIG_CC_OPTIMIZE_FOR_SIZE enabled this optimization does not happen anymore.

So we need a no-op ubifs_bad_hash() for the CONFIG_UBIFS_FS_AUTHENTICATION=n case.

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-11-21  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  8:33 [PATCH] ubifs: Fix build errors as symbol undefined Li Hua
2022-11-15  8:24 ` Zhihao Cheng
2022-11-19  5:21 ` Lihua (lihua, ran)
2022-11-19 21:25   ` Richard Weinberger
2022-11-21  1:54     ` Lihua (lihua, ran)
2022-11-21  8:00       ` Richard Weinberger [this message]
2022-11-21  9:32         ` Lihua (lihua, ran)

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=540631712.260900.1669017601995.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=hucool.lihua@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=weiyongjun1@huawei.com \
    --cc=yusongping@huawei.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).