Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-29 Thread Andreas Dilger
> On Nov 15, 2016, at 2:19 AM, Li Wang wrote: > > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type, it couldn't be > 4bits

Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-29 Thread Andreas Dilger
> On Nov 15, 2016, at 2:19 AM, Li Wang wrote: > > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type, it couldn't be > 4bits as the judgement in

Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-28 Thread Li Wang
sorry, ping for comments~ On 15 November 2016 at 17:19, Li Wang wrote: > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type,

Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-28 Thread Li Wang
sorry, ping for comments~ On 15 November 2016 at 17:19, Li Wang wrote: > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type, it couldn't be >

[PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-15 Thread Li Wang
put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW when some variables(like: f_bsize) overflowed in the returned struct. The reason is that the ubuf->f_blocks is __u64 type, it couldn't be 4bits as the judgement in put_comat_statfs64(). Here correct the __u32 variables(in

[PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

2016-11-15 Thread Li Wang
put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW when some variables(like: f_bsize) overflowed in the returned struct. The reason is that the ubuf->f_blocks is __u64 type, it couldn't be 4bits as the judgement in put_comat_statfs64(). Here correct the __u32 variables(in