From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q0CGdjiw006186 for ; Thu, 12 Jan 2012 10:39:45 -0600 Date: Thu, 12 Jan 2012 11:39:43 -0500 From: Christoph Hellwig Subject: Re: Introduce SEEK_DATA/SEEK_HOLE to XFS V5 Message-ID: <20120112163943.GA22223@infradead.org> References: <4F06F71A.2010301@oracle.com> <20120110171855.GX6390@sgi.com> <4F0D21E5.7010908@oracle.com> <4F0DFA11.7030305@sgi.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F0DFA11.7030305@sgi.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Mark Tinguely Cc: Christoph Hellwig , jeff.liu@oracle.com, Ben Myers , Chris Mason , xfs@oss.sgi.com On Wed, Jan 11, 2012 at 03:07:29PM -0600, Mark Tinguely wrote: > > xfs_bmapi_read() returns the br_state == XFS_EXT_NORM for a hole. > There are a couple places that a hole can trigger a data test. > BTW, I could not generate a large enough hole that xfs_bmapi_read() > would return as more than one hole entry, so I will ignore those > situations and just list the couple places that a hole may be match > a data rule: We've been through this before, you need to overflow the 32-bit extent length counter to get there. Jeff, did you manage to create a test case for that particular scenario? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs