From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] uimage: fix: add can_lseek_backward and use in uimage_open
Date: Fri, 10 Nov 2017 08:01:34 +0100 [thread overview]
Message-ID: <20171110070134.j2ydxid2j22nakvt@pengutronix.de> (raw)
In-Reply-To: <20171108180747.16208-1-m.grzeschik@pengutronix.de>
On Wed, Nov 08, 2017 at 07:07:47PM +0100, Michael Grzeschik wrote:
> Since commit ce0cc7fe we support forward seek on tftpfs. This feature
> breaks the condition to check rather we open an uimage over tftp. Since
> backward seeking is the problem here, we add the function
> can_lseek_backward and check for it instead of the simple lseek.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> v1 -> v2: - added can_lseek_backward
> - also fixed check in uimagefs
> - aligned comments to check
>
> common/uimage.c | 4 ++--
> fs/uimagefs.c | 4 ++--
> include/fs.h | 20 ++++++++++++++++++++
> 3 files changed, 24 insertions(+), 4 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/common/uimage.c b/common/uimage.c
> index 28a25bba2d..b6f0f109ca 100644
> --- a/common/uimage.c
> +++ b/common/uimage.c
> @@ -111,9 +111,9 @@ again:
> /*
> * Hack around tftp fs. We need lseek for uImage support, but
> * this cannot be implemented in tftp fs, so we detect this
> - * by doing a test lseek and copy the file to ram if it fails
> + * and copy the file to ram if it fails
> */
> - if (IS_BUILTIN(CONFIG_FS_TFTP) && lseek(fd, 0, SEEK_SET)) {
> + if (IS_BUILTIN(CONFIG_FS_TFTP) && !can_lseek_backward(fd)) {
> close(fd);
> ret = copy_file(filename, uimage_tmp, 0);
> if (ret)
> diff --git a/fs/uimagefs.c b/fs/uimagefs.c
> index 13c1fbac05..c0c5750c2c 100644
> --- a/fs/uimagefs.c
> +++ b/fs/uimagefs.c
> @@ -374,9 +374,9 @@ again:
> /*
> * Hack around tftp fs. We need lseek for uImage support, but
> * this cannot be implemented in tftp fs, so we detect this
> - * by doing a test lseek and copy the file to ram if it fails
> + * and copy the file to ram if it fails
> */
> - if (IS_BUILTIN(CONFIG_FS_TFTP) && lseek(fd, 0, SEEK_SET)) {
> + if (IS_BUILTIN(CONFIG_FS_TFTP) && !can_lseek_backward(fd)) {
> close(fd);
> ret = copy_file(priv->filename, priv->tmp, 0);
> if (ret)
> diff --git a/include/fs.h b/include/fs.h
> index d7fa7714b4..f8a3b8bda4 100644
> --- a/include/fs.h
> +++ b/include/fs.h
> @@ -100,6 +100,26 @@ struct fs_device_d {
> char *linux_rootarg;
> };
>
> +/*
> + * Some filesystems i.e. tftpfs only support lseek into one direction.
> + * To detect this limited functionality we add this extra function.
> + * Additionaly we also return 0 if we even can not seek forward.
> + */
> +static inline int can_lseek_backward(int fd)
> +{
> + int ret;
> +
> + ret = lseek(fd, 1, SEEK_SET);
> + if (ret < 0)
> + return 0;
> +
> + ret = lseek(fd, 0, SEEK_SET);
> + if (ret < 0)
> + return 0;
> +
> + return ret;
> +}
> +
> #define drv_to_fs_driver(d) container_of(d, struct fs_driver_d, drv)
>
> int flush(int fd);
> --
> 2.11.0
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-11-10 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 18:07 Michael Grzeschik
2017-11-10 7:01 ` Sascha Hauer [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=20171110070134.j2ydxid2j22nakvt@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.grzeschik@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox