mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] tftp: implement forward seeking
Date: Fri, 3 Mar 2017 11:52:05 +0100	[thread overview]
Message-ID: <20170303105205.q3q4t7m7xznlsdcw@pengutronix.de> (raw)
In-Reply-To: <20170303084841.28907-1-u.kleine-koenig@pengutronix.de>

On Fri, Mar 03, 2017 at 09:48:41AM +0100, Uwe Kleine-König wrote:
> Just abuse tftp_read to step forward.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> this is v2 which compared to (implicit) v1 uses xmalloc and no debugging
> any more.
> 
> When tftp_lseek is entered with f->pos == pos, the only thing that the
> function does is xmalloc, free, return. Is it worth to optimize that?
> I thought it's not worth the additional (even if trivial) complication,
> but want to at least point that out.

I don' think that's worth optimizing.

Applied, thanks

Sascha

> 
> Best regards
> Uwe
> 
>  fs/tftp.c | 27 ++++++++++++++++++++++++++-
>  1 file changed, 26 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/tftp.c b/fs/tftp.c
> index 56d4365d773a..4bacd2ed7fcf 100644
> --- a/fs/tftp.c
> +++ b/fs/tftp.c
> @@ -591,7 +591,32 @@ static int tftp_read(struct device_d *dev, FILE *f, void *buf, size_t insize)
>  
>  static loff_t tftp_lseek(struct device_d *dev, FILE *f, loff_t pos)
>  {
> -	/* not implemented in tftp protocol */
> +	/* We cannot seek backwards without reloading or caching the file */
> +	if (pos >= f->pos) {
> +		loff_t ret;
> +		char *buf = xmalloc(1024);
> +
> +		while (pos > f->pos) {
> +			size_t len = min_t(size_t, 1024, pos - f->pos);
> +
> +			ret = tftp_read(dev, f, buf, len);
> +
> +			if (!ret)
> +				/* EOF, so the desired pos is invalid. */
> +				ret = -EINVAL;
> +			if (ret < 0)
> +				goto out_free;
> +
> +			f->pos += ret;
> +		}
> +
> +		ret = pos;
> +
> +out_free:
> +		free(buf);
> +		return ret;
> +	}
> +
>  	return -ENOSYS;
>  }
>  
> -- 
> 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

      reply	other threads:[~2017-03-03 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  8:48 Uwe Kleine-König
2017-03-03 10:52 ` 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=20170303105205.q3q4t7m7xznlsdcw@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@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