On 4.11.2017 06:07, fdmanana@xxxxxxxxxx wrote: > From: Filipe Manana <fdmanana@xxxxxxxx> > > This implements support the zero range operation of fallocate. For now > at least it's as simple as possible while reusing most of the existing > fallocate and hole punching infrastructure. > > Signed-off-by: Filipe Manana <fdmanana@xxxxxxxx> > --- > > V2: Removed double inode unlock on error path from failure to lock range. > V3: Factored common code to update isize and inode item into a helper > function, plus some minor cleanup. > V4: Removed no longer lock_inode parameter as of V3. > When this gets merged into Linus' tree we'd need to update fallocate's man page as well -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
