From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: christian.thiessen@airbus.com, BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH] mtd: Make mtd_erase fail gracefully if CONFIG_MTD_WRITE is off
Date: Wed, 3 Sep 2025 12:11:02 +0200 [thread overview]
Message-ID: <e49d3dc6-054f-406c-8fe8-45cbd617036d@pengutronix.de> (raw)
In-Reply-To: <20250903-mtd-erase-enosys-v1-1-967a95172c4e@airbus.com>
Hi Christian,
Thanks for your patch!
On 9/3/25 10:49 AM, Christian Thießen via B4 Relay wrote:
> From: Christian Thießen <christian.thiessen@airbus.com>
>
> When CONFIG_MTD_WRITE is unset, the mtd->_erase member of partition
> devices does not get initialized, so it remains NULL.
> However when running ubiattach on an UBI partition, mtd_erase() still
> gets called, tries to call mtd->_erase and crashes. Make it fail
> gracefully by returning ENOSYS ("Function not implemented") instead.
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
with two minor comments below.
>
> ---
> As discussed in https://github.com/barebox/barebox/issues/39 this patch
> enables ubiattach-ing a NAND partition even if CONFIG_MTD_WRITE is
> turned off, by making mtd_erase fail gracefully.
>
> Signed-off-by: Christian Thießen <christian.thiessen@airbus.com>
Stuff between the --- is thrown away by git am, so you will want to move
the S-o-b above the ---. The rest is okay.
> ---
> drivers/mtd/core.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mtd/core.c b/drivers/mtd/core.c
> index 6162ec450fc1c3a0fa6339042c4d627e0f9567d0..7ca8fc900af4666070b03ef5f945748d60e6a6e7 100644
> --- a/drivers/mtd/core.c
> +++ b/drivers/mtd/core.c
> @@ -436,6 +436,7 @@ int mtd_erase(struct mtd_info *mtd, struct erase_info *instr)
> {
> if (instr->addr >= mtd->size || instr->len > mtd->size - instr->addr)
> return -EINVAL;
> +#ifdef CONFIG_MTD_WRITE
Please replace with the following at the start of the function:
if (!IS_ENABLED(CONFIG_MTD_WRITE))
return -ENOSYS;
This results in the same code as IS_ENABLED() is evaluated at
compile-time. but the compiler can still catch compile errors in the
disabled parts, which makes maintenance easier.
Cheers,
Ahmad
> if (!(mtd->flags & MTD_WRITEABLE))
> return -EROFS;
> instr->fail_addr = MTD_FAIL_ADDR_UNKNOWN;
> @@ -443,6 +444,9 @@ int mtd_erase(struct mtd_info *mtd, struct erase_info *instr)
> return 0;
>
> return mtd->_erase(mtd, instr);
> +#else
> + return -ENOSYS;
> +#endif
> }
>
> int mtd_read_oob(struct mtd_info *mtd, loff_t from, struct mtd_oob_ops *ops)
>
> ---
> base-commit: b5561f3bdd4845b478e5b35aab04f1d8e71ea93b
> change-id: 20250902-mtd-erase-enosys-2d80e4bc77c8
>
> Best regards,
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-09-03 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 8:49 Christian Thießen via B4 Relay
2025-09-03 10:11 ` Ahmad Fatoum [this message]
2025-09-03 11:05 ` Marco Felsch
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=e49d3dc6-054f-406c-8fe8-45cbd617036d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=christian.thiessen@airbus.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