From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: [PATCH 0/2] Add FALLOC_FL_ZERO_RANGE to fallocate Date: Wed, 13 Jun 2012 11:35:49 +1000 Message-ID: <20120613013549.GO22848@dastard> References: <1339515364-17374-1-git-send-email-pbonzini@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro , xfs@oss.sgi.com To: Paolo Bonzini Return-path: Content-Disposition: inline In-Reply-To: <1339515364-17374-1-git-send-email-pbonzini@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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@fromorbit.com