From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Arnd Bergmann <arnd@kernel.org>,
Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Ben Hutchings <ben.hutchings@mind.be>
Cc: Arnd Bergmann <arnd@arndb.de>, Li Nan <linan122@huawei.com>,
Daniel Golle <daniel@makrotopia.org>,
Jens Axboe <axboe@kernel.dk>,
ZhaoLong Wang <wangzhaolong1@huawei.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: ubi: remove __exit annotation on ubiblock_exit
Date: Fri, 19 Jul 2024 16:09:53 +0800 [thread overview]
Message-ID: <92d8047d-1bee-d100-fd3f-ec27f030b1e5@huawei.com> (raw)
In-Reply-To: <20240719073912.2743171-1-arnd@kernel.org>
在 2024/7/19 15:39, Arnd Bergmann 写道:
Hi, Arnd
> From: Arnd Bergmann <arnd@arndb.de>
>
> Calling an __exit function from an __init function leads to undefined behavior
> when the drier is built-in and the __exit functions are dropped from the
> object:
>
> WARNING: modpost: drivers/mtd/ubi/ubi: section mismatch in reference: ubi_init+0xbe (section: .init.text) -> ubiblock_exit (section: .exit.text)
> ERROR: modpost: Section mismatches detected.
> Set CONFIG_SECTION_MISMATCH_WARN_ONLY=y to allow them.
>
> Remove the now incorrect annotation.
>
> Fixes: 72f3d3daddd7 ("mtd: ubi: Restore missing cleanup on ubi_init() failure path")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/mtd/ubi/block.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Richard has sent the same modification, see
https://lore.kernel.org/linux-mtd/9a210424-eac1-957e-dd6e-4290924216e3@huawei.com/T/#mdefbd793992635f6a236a626dd7d3a296fb9820e
>
> diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c
> index bf7308e8ec2f..60d0155be869 100644
> --- a/drivers/mtd/ubi/block.c
> +++ b/drivers/mtd/ubi/block.c
> @@ -670,7 +670,7 @@ int __init ubiblock_init(void)
> return ret;
> }
>
> -void __exit ubiblock_exit(void)
> +void ubiblock_exit(void)
> {
> ubi_unregister_volume_notifier(&ubiblock_notifier);
> ubiblock_remove_all();
>
prev parent reply other threads:[~2024-07-19 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 7:39 Arnd Bergmann
2024-07-19 8:09 ` 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=92d8047d-1bee-d100-fd3f-ec27f030b1e5@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=axboe@kernel.dk \
--cc=ben.hutchings@mind.be \
--cc=daniel@makrotopia.org \
--cc=linan122@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wangzhaolong1@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
all inboxes | Powered by JetHome®