[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKYAXd8wLuSevrKqyztNVM47OT-fwhJ41cnuU7K8+n4ezQFf_A@mail.gmail.com>
Date: Thu, 5 Dec 2013 23:21:42 +0900
From: Namjae Jeon <linkinjeon@...il.com>
To: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Cc: akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, Namjae Jeon <namjae.jeon@...sung.com>
Subject: Re: [PATCH v2 0/5] fat: additions to support fat_fallocate
2013/12/1, OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>:
> Namjae Jeon <linkinjeon@...il.com> writes:
>
>> From: Namjae Jeon <namjae.jeon@...sung.com>
>>
>> This patch set provides support for doing fallocate operation
>> on FAT filesystem.
>> After series of review for the the feature
>> The complete functionality is broken down into smaller subsets.
>>
>> v2:
>> - remove a stary unlock(from Dan Carpenter)
>> - check ->mmu_private and ->i_disksize to truncate uninitialized data.
>>
>> Namjae Jeon (5):
>> fat: add i_disksize to represent uninitialized size
>> fat: add fat_fallocate operation
>> fat: zero out seek range on _fat_get_block
>> fat: fallback to buffered write in case of fallocatded region on direct
>> IO
>> fat: permit to return phy block number by fibmap in fallocated region
>
> Let's add document about FAT's fallocate() behavior to
> Documents/filesystem/vfat.txt.
>
> I.e. it will be truncated evict_inode(). So, user has to assume
> fallocate() is only valid until last close(), and user has to re-call
> fallocate() after re-open to make sure fallocate() region.
Right. I will update vfat document.
Thanks for review.
> --
> OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists