> > On Wed, Dec 10, 2014 at 07:42:16PM +0900, Namjae Jeon wrote: > > User have to call fallocate again if opening file after close(). > > And fallocate() will skip allocation if fallocated blocks is avaiable. > > Instead, It gurrantee to be available fallocated blocks between open > > and close(). And I updated such limitation of fat fallocate in > > Documentation. > > Documentation doesn't help, this breaks application exposed semantics. > > If you think there is a use case for non-persistant preallocations > please propose a new fallocate flag for it, or given the lack of use > case probably just add a fat specific ioctl instead. Hi Christoph, Yes, There are use cases from me and samba team also. And it is fat's specific limitation. so looks better to add ioctl. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
