| To: | Paolo Bonzini <pbonzini@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 0/2] Add FALLOC_FL_ZERO_RANGE to fallocate |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 13 Jun 2012 11:35:49 +1000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <1339515364-17374-1-git-send-email-pbonzini@xxxxxxxxxx> |
| References: | <1339515364-17374-1-git-send-email-pbonzini@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Jun 12, 2012 at 05:36:02PM +0200, Paolo Bonzini wrote: > This patch adds the FALLOC_FL_ZERO_RANGE operation mode to fallocate, > resembling the similar XFS ioctl. The new mode can be used with > or without FALLOC_FL_KEEP_SIZE, but of course not together with > FALLOC_FL_PUNCH_HOLE. !FALLOC_FL_KEEP_SIZE makes no sense for this operation. It is for zeroing an existing section of a file while retaining the allocated space, not for extending or truncating the file. It's the same reason that FALLOC_FL_PUNCH_HOLE must have FALLOC_FL_KEEP_SIZE set. Also, a minor nit, but you should credit where this code has originated from in the commit messages, and describe the use case for requiring it. i.e. based on: http://permalink.gmane.org/gmane.linux.file-systems/62449 Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS hangs and freezes with LSI 9265-8i controller on high i/o, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH 1/2] vfs: add FALLOC_FL_ZERO_RANGE to fallocate, Dave Chinner |
| Previous by Thread: | Re: [PATCH 2/2] xfs: add FALLOC_FL_ZERO_RANGE to fallocate, Dave Chinner |
| Next by Thread: | Re: [PATCH 0/2] Add FALLOC_FL_ZERO_RANGE to fallocate, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |