[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E5DBBFD.5020202@oracle.com>
Date: Tue, 30 Aug 2011 21:43:41 -0700
From: Sunil Mushran <sunil.mushran@...cle.com>
To: Dave Chinner <david@...morbit.com>
CC: Andreas Dilger <adilger@...ger.ca>,
Christoph Hellwig <hch@...radead.org>,
Josef Bacik <josef@...hat.com>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
xfs@....sgi.com, viro@...IV.linux.org.uk, dchinner@...hat.com
Subject: Re: [PATCH] xfstests 255: add a seek_data/seek_hole tester
On 8/30/2011 8:29 PM, Dave Chinner wrote:
> And that's -exactly- the ambiguous, vague definition that has raised
> all these questions in the first place. I was in doubt about whether
> unwritten extents can be considered a hole, and by your definition
> that means it should be data. But Andreas seems to be in no doubt it
> should be considered a hole.
Fair enough. Let me rephrase.
Data:
A range in a file when read could return something other than nulls.
Hole:
A range in a file when read only returns nulls.
Considering preallocated extents only return null, they should
be considered holes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists