ext4: use consistent ssize_t type in ext4_file_write()
authorZheng Liu <gnehzuil.liu@gmail.com>
Mon, 28 May 2012 22:06:51 +0000 (18:06 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Mon, 28 May 2012 22:06:51 +0000 (18:06 -0400)
commit8563000d3bf3ccfccce335c092a7c43078be8ffd
tree393a35a5504527f0e98e8c82cbac259fd886c766
parent4a3c3a5120bff77cc8c3a70c7cb681f458f47bfd
ext4: use consistent ssize_t type in ext4_file_write()

The generic_file_aio_write() function returns ssize_t, and
ext4_file_write() returns a ssize_t, so use a ssize_t to collect the
return value from generic_file_aio_write().  It shouldn't matter since
the VFS read/write paths shouldn't allow a read greater than MAX_INT,
but there was previously a bug in the AIO code paths, and it's best if
we use a consistent type so that the return value from
generic_file_aio_write() can't get truncated.

Reported-by: Jouni Siren <jouni.siren@iki.fi>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/ext4/file.c