On 2017/3/22 22:21, Jaegeuk Kim wrote:
> On 03/22, Chao Yu wrote:
>> On 2017/3/22 16:42, Chao Yu wrote:
>>> On 2017/3/22 0:18, Jaegeuk Kim wrote:
On 03/20, Kinglong Mee wrote:
> On 3/20/2017 11:08, Jaegeuk Kim wrote:
>> Hi Kinglong,
>>
>> On 03/18, Kinglong Mee wrote:
>>>
On 03/22, Chao Yu wrote:
> On 2017/3/22 16:42, Chao Yu wrote:
> > On 2017/3/22 0:18, Jaegeuk Kim wrote:
> >> On 03/20, Kinglong Mee wrote:
> >>> On 3/20/2017 11:08, Jaegeuk Kim wrote:
> Hi Kinglong,
>
> On 03/18, Kinglong Mee wrote:
> > It's better coping all valid xattr data
On 3/22/2017 18:16, Chao Yu wrote:
> On 2017/3/22 16:42, Chao Yu wrote:
>> On 2017/3/22 0:18, Jaegeuk Kim wrote:
>>> On 03/20, Kinglong Mee wrote:
On 3/20/2017 11:08, Jaegeuk Kim wrote:
> Hi Kinglong,
>
> On 03/18, Kinglong Mee wrote:
>> It's better coping all valid xattr data
On 2017/3/22 16:42, Chao Yu wrote:
> On 2017/3/22 0:18, Jaegeuk Kim wrote:
>> On 03/20, Kinglong Mee wrote:
>>> On 3/20/2017 11:08, Jaegeuk Kim wrote:
Hi Kinglong,
On 03/18, Kinglong Mee wrote:
> It's better coping all valid xattr data includes the last zero.
Why do
On 3/20/2017 11:08, Jaegeuk Kim wrote:
> Hi Kinglong,
>
> On 03/18, Kinglong Mee wrote:
>> It's better coping all valid xattr data includes the last zero.
>
> Why do we need this?
>
> The size of txattr_addr would be larger than the space we need.
>
> Thanks,
>
>>
>> Signed-off-by: Kinglong
Hi Kinglong,
On 03/18, Kinglong Mee wrote:
> It's better coping all valid xattr data includes the last zero.
Why do we need this?
The size of txattr_addr would be larger than the space we need.
Thanks,
>
> Signed-off-by: Kinglong Mee
> ---
> fs/f2fs/xattr.c | 4 ++--
It's better coping all valid xattr data includes the last zero.
Signed-off-by: Kinglong Mee
---
fs/f2fs/xattr.c | 4 ++--
fs/f2fs/xattr.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/xattr.c b/fs/f2fs/xattr.c
index aff7619..41785c9