From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v3 8/9] fs: Report errors for out-of-bounds protect operations
Date: Tue, 17 Jun 2025 09:56:41 +0200 [thread overview]
Message-ID: <aFEfuaLIvT8cMLLA@pengutronix.de> (raw)
In-Reply-To: <20250612065812.2025665-9-o.rempel@pengutronix.de>
On Thu, Jun 12, 2025 at 08:58:11AM +0200, Oleksij Rempel wrote:
> The protect() function previously masked errors for out-of-bounds
> requests. It would either return success for offsets already beyond
> file/partition size or clamp the count for ranges extending beyond the
> boundary. This behavior was introduced by commit 6815e0d05480 ("fs:
> limit flash erase and protect to the partiton boundary") to address SPI
> flash wrap-around issues.
>
> This masking prevented shell commands from reporting failures for
> invalid ranges, which could mislead users and scripts. For example,
> underlying driver errors like -EINVAL from NVMEM were not propagated.
>
> This patch modifies protect() to return appropriate error codes (-ENXIO
> or -EINVAL) for such out-of-bounds conditions, instead of silently
> succeeding or clamping.
>
> Fixes: 6815e0d05480 ("fs: limit flash erase and protect to the partiton boundary")
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> fs/fs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/fs.c b/fs/fs.c
> index 7bc94d7b9e6c..dd6af3cef874 100644
> --- a/fs/fs.c
> +++ b/fs/fs.c
> @@ -652,9 +652,9 @@ int protect(int fd, size_t count, loff_t offset, int prot)
> if (IS_ERR(f))
> return -errno;
> if (offset >= f->f_size)
> - return 0;
> - if (count > f->f_size - offset)
> - count = f->f_size - offset;
> + return errno_set(-ENXIO);
> + if (!count || count > f->f_size - offset)
> + return errno_set(-EINVAL);
This breaks the saveenv command which does a
ret = protect(envfd, ~0, 0, 0);
to unprotect the environment sector. Try on a board with environment in
SPI flash.
Sascha
--
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-06-17 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 6:58 [PATCH v3 0/9] NVMEM: Introduce write protection support Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 1/9] nvmem: Add 'protect' operation to core framework Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 2/9] nvmem: rmem: add write and protect support Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 3/9] commands: nvmem: Add support for creating dynamic rmem devices Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 4/9] regmap: Add reg_seal operation for hardware protection Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 5/9] nvmem: regmap: Implement protect operation using regmap_seal Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 6/9] nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 7/9] nvmem: rmem: ensure unique device name per instance Oleksij Rempel
2025-06-12 6:58 ` [PATCH v3 8/9] fs: Report errors for out-of-bounds protect operations Oleksij Rempel
2025-06-17 7:56 ` Sascha Hauer [this message]
2025-06-25 5:45 ` Ahmad Fatoum
2025-06-25 7:11 ` Sascha Hauer
2025-06-12 6:58 ` [PATCH v3 9/9] test: Add pytest suite for NVMEM framework Oleksij Rempel
2025-06-17 8:03 ` Sascha Hauer
2025-06-17 8:17 ` Oleksij Rempel
2025-06-17 8:04 ` (subset) [PATCH v3 0/9] NVMEM: Introduce write protection support Sascha Hauer
2025-06-23 11:59 ` Sascha Hauer
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=aFEfuaLIvT8cMLLA@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=o.rempel@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.