* [PATCH master] fs: align truncate return codes with POSIX
@ 2023-02-02 12:20 Ahmad Fatoum
2023-02-02 13:12 ` Marco Felsch
2023-02-03 7:52 ` Sascha Hauer
0 siblings, 2 replies; 3+ messages in thread
From: Ahmad Fatoum @ 2023-02-02 12:20 UTC (permalink / raw)
To: barebox; +Cc: Marco Felsch, Ahmad Fatoum
Writing past end of a file results in a cryptic error code:
barebox@board:/ cp /dev/zero /dev/mmc0.part
write: Operation not permitted
cp: Operation not permitted
Because the cdev's truncate is not implemented and as such partition
can't be increased in size. POSIX specifies EPERM as the correct return
code for truncate(2) in such a situation, but for write(2) it is ENOSPC.
Thus most truncate callbacks in barebox instead return ENOSPC, when
according to POSIX, EPERM would have been the correct error code to
propagate.
Switching all truncate drivers is a bit more involved, so for now let's
treat EPERM and ENOSPC instead when truncate fails to enlarge a file.
Reported-by: Marco Felsch <m.felsch@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
fs/fs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/fs.c b/fs/fs.c
index 752688b574a0..c463466e1be0 100644
--- a/fs/fs.c
+++ b/fs/fs.c
@@ -441,6 +441,8 @@ static ssize_t __write(FILE *f, const void *buf, size_t count)
if (f->size != FILE_SIZE_STREAM && f->pos + count > f->size) {
ret = fsdev_truncate(&f->fsdev->dev, f, f->pos + count);
if (ret) {
+ if (ret == -EPERM)
+ ret = -ENOSPC;
if (ret != -ENOSPC)
goto out;
count = f->size - f->pos;
--
2.30.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH master] fs: align truncate return codes with POSIX
2023-02-02 12:20 [PATCH master] fs: align truncate return codes with POSIX Ahmad Fatoum
@ 2023-02-02 13:12 ` Marco Felsch
2023-02-03 7:52 ` Sascha Hauer
1 sibling, 0 replies; 3+ messages in thread
From: Marco Felsch @ 2023-02-02 13:12 UTC (permalink / raw)
To: Ahmad Fatoum; +Cc: barebox
Hi Ahmad,
thanks for the patch.
On 23-02-02, Ahmad Fatoum wrote:
> Writing past end of a file results in a cryptic error code:
>
> barebox@board:/ cp /dev/zero /dev/mmc0.part
> write: Operation not permitted
> cp: Operation not permitted
>
> Because the cdev's truncate is not implemented and as such partition
> can't be increased in size. POSIX specifies EPERM as the correct return
> code for truncate(2) in such a situation, but for write(2) it is ENOSPC.
> Thus most truncate callbacks in barebox instead return ENOSPC, when
> according to POSIX, EPERM would have been the correct error code to
> propagate.
>
> Switching all truncate drivers is a bit more involved, so for now let's
> treat EPERM and ENOSPC instead when truncate fails to enlarge a file.
>
> Reported-by: Marco Felsch <m.felsch@pengutronix.de>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH master] fs: align truncate return codes with POSIX
2023-02-02 12:20 [PATCH master] fs: align truncate return codes with POSIX Ahmad Fatoum
2023-02-02 13:12 ` Marco Felsch
@ 2023-02-03 7:52 ` Sascha Hauer
1 sibling, 0 replies; 3+ messages in thread
From: Sascha Hauer @ 2023-02-03 7:52 UTC (permalink / raw)
To: Ahmad Fatoum; +Cc: barebox, Marco Felsch
On Thu, Feb 02, 2023 at 01:20:00PM +0100, Ahmad Fatoum wrote:
> Writing past end of a file results in a cryptic error code:
>
> barebox@board:/ cp /dev/zero /dev/mmc0.part
> write: Operation not permitted
> cp: Operation not permitted
>
> Because the cdev's truncate is not implemented and as such partition
> can't be increased in size. POSIX specifies EPERM as the correct return
> code for truncate(2) in such a situation, but for write(2) it is ENOSPC.
> Thus most truncate callbacks in barebox instead return ENOSPC, when
> according to POSIX, EPERM would have been the correct error code to
> propagate.
>
> Switching all truncate drivers is a bit more involved, so for now let's
> treat EPERM and ENOSPC instead when truncate fails to enlarge a file.
>
> Reported-by: Marco Felsch <m.felsch@pengutronix.de>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> fs/fs.c | 2 ++
> 1 file changed, 2 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/fs/fs.c b/fs/fs.c
> index 752688b574a0..c463466e1be0 100644
> --- a/fs/fs.c
> +++ b/fs/fs.c
> @@ -441,6 +441,8 @@ static ssize_t __write(FILE *f, const void *buf, size_t count)
> if (f->size != FILE_SIZE_STREAM && f->pos + count > f->size) {
> ret = fsdev_truncate(&f->fsdev->dev, f, f->pos + count);
> if (ret) {
> + if (ret == -EPERM)
> + ret = -ENOSPC;
> if (ret != -ENOSPC)
> goto out;
> count = f->size - f->pos;
> --
> 2.30.2
>
>
>
--
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 |
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-02-03 7:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-02 12:20 [PATCH master] fs: align truncate return codes with POSIX Ahmad Fatoum
2023-02-02 13:12 ` Marco Felsch
2023-02-03 7:52 ` Sascha Hauer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox