public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] configfs: use capped length for ->store_attribute()
Date: Thu, 2 May 2013 14:51:53 -0700	[thread overview]
Message-ID: <20130502215152.GB26770@localhost> (raw)
In-Reply-To: <20130430072813.GC7237@elgon.mountain>

On Tue, Apr 30, 2013 at 10:28:14AM +0300, Dan Carpenter wrote:
> The difference between "count" and "len" is that "len" is capped at
> 4095.  Changing it like this makes it match how sysfs_write_file() is
> implemented.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Acked-by: Joel Becker <jlbec@evilplan.org>

Do you want me to push this up, or will you be sending it?

Joel


> ---
> This is a static analysis patch.  I haven't found any store_attribute()
> functions where this change makes a difference.
> 
> diff --git a/fs/configfs/file.c b/fs/configfs/file.c
> index 2b6cb23..1d1c41f 100644
> --- a/fs/configfs/file.c
> +++ b/fs/configfs/file.c
> @@ -203,7 +203,7 @@ configfs_write_file(struct file *file, const char __user *buf, size_t count, lof
>  	mutex_lock(&buffer->mutex);
>  	len = fill_write_buffer(buffer, buf, count);
>  	if (len > 0)
> -		len = flush_write_buffer(file->f_path.dentry, buffer, count);
> +		len = flush_write_buffer(file->f_path.dentry, buffer, len);
>  	if (len > 0)
>  		*ppos += len;
>  	mutex_unlock(&buffer->mutex);

-- 

"In the room the women come and go
 Talking of Michaelangelo."

			http://www.jlbec.org/
			jlbec@evilplan.org

  reply	other threads:[~2013-05-02 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  7:28 [patch] configfs: use capped length for ->store_attribute() Dan Carpenter
2013-05-02 21:51 ` Joel Becker [this message]
2013-05-02 22:00   ` Dan Carpenter

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=20130502215152.GB26770@localhost \
    --to=jlbec@evilplan.org \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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