From: Eric Sandeen <sandeen@redhat.com>
To: Zheng Liu <gnehzuil.liu@gmail.com>
Cc: jack@suse.cz, jouni.siren@iki.fi, linux-ext4@vger.kernel.org,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH RESEND] ext4: change return value from int to ssize_t in ext4_file_write
Date: Tue, 22 May 2012 14:44:03 -0500 [thread overview]
Message-ID: <4FBBEC83.8030604@redhat.com> (raw)
In-Reply-To: <1334280157-11630-1-git-send-email-wenqing.lz@taobao.com>
On 4/12/12 8:22 PM, Zheng Liu wrote:
> On 64-platform, when we do a write operation with a huge number of data, it
> will cause that the ret variable overflows. So it is replaced with ssize_t.
>
> Reported-by: Jouni Siren <jouni.siren@iki.fi>
> Reviewed-by: Jan Kara <jack@suse.cz>
> Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
Ted, is this one queued anywhere? Seems lost so far.
Thanks,
-Eric
> ---
> Hi Jan,
>
> You are right. I have changed the commit log. ;-)
>
> Regards,
> Zheng
>
> fs/ext4/file.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext4/file.c b/fs/ext4/file.c
> index cb70f18..8c7642a 100644
> --- a/fs/ext4/file.c
> +++ b/fs/ext4/file.c
> @@ -95,7 +95,7 @@ ext4_file_write(struct kiocb *iocb, const struct iovec *iov,
> {
> struct inode *inode = iocb->ki_filp->f_path.dentry->d_inode;
> int unaligned_aio = 0;
> - int ret;
> + ssize_t ret;
>
> /*
> * If we have encountered a bitmap-format file, the size limit
next prev parent reply other threads:[~2012-05-22 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 14:47 Bug: Large writes can fail on ext4 if the write buffer is not empty Jouni Siren
2012-04-12 16:06 ` Zheng Liu
2012-04-12 20:20 ` Jan Kara
2012-04-13 1:22 ` [PATCH RESEND] ext4: change return value from int to ssize_t in ext4_file_write Zheng Liu
2012-05-22 19:44 ` Eric Sandeen [this message]
2012-05-28 22:08 ` Ted Ts'o
2012-04-19 13:10 ` Bug: Large writes can fail on ext4 if the write buffer is not empty Jouko Orava
2012-04-19 14:15 ` Eric Sandeen
2012-04-19 14:38 ` Jouko Orava
2012-04-19 14:45 ` Eric Sandeen
2012-04-19 15:09 ` Jouko Orava
2012-04-19 15:28 ` Zheng Liu
2012-04-20 2:12 ` Dave Chinner
2012-04-19 14:56 ` Zheng Liu
2012-04-13 0:10 ` Dave Chinner
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=4FBBEC83.8030604@redhat.com \
--to=sandeen@redhat.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jack@suse.cz \
--cc=jouni.siren@iki.fi \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.