From: Stefan Bruens <stefan.bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ext4: Allow reading files with non-zero offset, clamp read len
Date: Sun, 6 Nov 2016 18:12:58 +0100 [thread overview]
Message-ID: <22068908.cRyZAGdtvO@pebbles.site> (raw)
In-Reply-To: <41684559-0411-4187-3b5e-0d770c3abc92@wwwdotorg.org>
On Samstag, 5. November 2016 21:22:43 CET Stephen Warren wrote:
> On 11/05/2016 06:32 PM, Stefan Br?ns wrote:
> > Support was already implemented, but not hooked up. This fixes several
> > fails in the test cases.
> >
> > diff --git a/fs/ext4/ext4fs.c b/fs/ext4/ext4fs.c
> >
> > @@ -217,21 +217,16 @@ int ext4_read_file(const char *filename, void *buf,
> > loff_t offset, loff_t len,
> >
> > - if (len == 0)
> > - len = file_len;
> > + if ((len == 0) || (offset + len > file_len))
> > + len = (file_len - offset);
>
> Isn't (offset + len > file_len) an error? It seems find to "read to EOF"
> if the caller specified len==0, but if they specified a specific len,
> then isn't it an error if len+offset exceeds the length of the file?
>
> On the other hand, if this is how other filesystems work in U-Boot, it's
> fine. I suppose this is consistent with how POSIX read() works.
It matches behaviour of POSIX read() and u-boot's FAT implementation, and
there is also the actread parameter the caller could/should check.
> > diff --git a/include/ext4fs.h b/include/ext4fs.h
> >
> > -int ext4fs_read(char *buf, loff_t len, loff_t *actread);
> > +int ext4fs_read(char *buf, loff_t offset, loff_t len, loff_t *actread);
>
> Don't you need to update all callers of this function in this patch so
> the build doesn't break?
Missed the calls from spl_ext.c, will send v2.
Kind regards,
Stefan
--
Stefan Br?ns / Bergstra?e 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
work: +49 2405 49936-424
prev parent reply other threads:[~2016-11-06 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 0:32 [U-Boot] [PATCH 1/2] ext4: Allow reading files with non-zero offset, clamp read len Stefan Brüns
2016-11-06 3:22 ` Stephen Warren
2016-11-06 17:12 ` Stefan Bruens [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=22068908.cRyZAGdtvO@pebbles.site \
--to=stefan.bruens@rwth-aachen.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox