devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Geert Uytterhoeven
	<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>,
	Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
	Pantelis Antoniou
	<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] configfs: Remove ppos increment in configfs_write_bin_file
Date: Tue, 28 Jun 2016 18:30:28 +0200	[thread overview]
Message-ID: <5772A624.6040801@denx.de> (raw)
In-Reply-To: <1463581011-9910-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>

On 05/18/2016 04:16 PM, Marek Vasut wrote:
> The simple_write_to_buffer() already increments the @ppos on success,
> see fs/libfs.c simple_write_to_buffer() comment:
> 
> "
> On success, the number of bytes written is returned and the offset @ppos
> advanced by this number, or negative value is returned on error.
> "
> 
> If the configfs_write_bin_file() is invoked with @count smaller than the
> total length of the written binary file, it will be invoked multiple times.
> Since configfs_write_bin_file() increments @ppos on success, after calling
> simple_write_to_buffer(), the @ppos is incremented twice.
> 
> Subsequent invocation of configfs_write_bin_file() will result in the next
> piece of data being written to the offset twice as long as the length of
> the previous write, thus creating buffer with "holes" in it.
> 
> The simple testcase using DTO follows:
>   $ mkdir /sys/kernel/config/device-tree/overlays/1
>   $ dd bs=1 if=foo.dtbo of=/sys/kernel/config/device-tree/overlays/1/dtbo
> Without this patch, the testcase will result in twice as big buffer in the
> kernel, which is then passed to the cfs_overlay_item_dtbo_write() .
> 
> Signed-off-by: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
> Cc: Geert Uytterhoeven <geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
> Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> Cc: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>

Bump, could this be applied please ?

> ---
>  fs/configfs/file.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/fs/configfs/file.c b/fs/configfs/file.c
> index 33b7ee3..bbc1252 100644
> --- a/fs/configfs/file.c
> +++ b/fs/configfs/file.c
> @@ -357,8 +357,6 @@ configfs_write_bin_file(struct file *file, const char __user *buf,
>  
>  	len = simple_write_to_buffer(buffer->bin_buffer,
>  			buffer->bin_buffer_size, ppos, buf, count);
> -	if (len > 0)
> -		*ppos += len;
>  out:
>  	mutex_unlock(&buffer->mutex);
>  	return len;
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-06-28 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 14:16 [PATCH] configfs: Remove ppos increment in configfs_write_bin_file Marek Vasut
     [not found] ` <1463581011-9910-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2016-06-28 16:30   ` Marek Vasut [this message]
     [not found]     ` <5772A624.6040801-ynQEQJNshbs@public.gmane.org>
2016-06-30  9:26       ` Christoph Hellwig
     [not found]         ` <20160630092616.GA9099-jcswGhMUV9g@public.gmane.org>
2016-06-30 12:51           ` Marek Vasut
     [not found]             ` <577515C6.5050802-ynQEQJNshbs@public.gmane.org>
2016-06-30 14:19               ` Christoph Hellwig
     [not found]                 ` <20160630141948.GA19378-jcswGhMUV9g@public.gmane.org>
2016-06-30 14:35                   ` Marek Vasut

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=5772A624.6040801@denx.de \
    --to=marex-ynqeqjnshbs@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).