linux-kernel - Re: [PATCH] fallocate.2: add FALLOC_FL_PUNCH

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110919063226.GI15688@dastard>
Date:	Mon, 19 Sep 2011 16:32:26 +1000
From:	Dave Chinner <david@...morbit.com>
To:	Michael Kerrisk <mtk.manpages@...il.com>
Cc:	Josef Bacik <josef@...hat.com>, linux-man@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Lucian Adrian Grijincu <lucian.grijincu@...il.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Dave Chinner <dchinner@...hat.com>
Subject: Re: [PATCH] fallocate.2: add FALLOC_FL_PUNCH_HOLE flag definition

On Mon, Sep 19, 2011 at 07:08:17AM +0200, Michael Kerrisk wrote:
> Hi Josef (Dave C, please also note comments below),
> 
> On Mon, Nov 15, 2010 at 6:07 PM, Josef Bacik <josef@...hat.com> wrote:
> > This patch adds the relevant documenation for using fallocate with the
> > FALLOC_FL_PUNCH_HOLE mode.  This information comes from the implementation of
> > FALLOC_FL_PUNCH_HOLE that I've posted along with this man page update to outline
> > the definition for hole punching.  Obviously this patch is dependant upon the
> > current implementation being accepted.  Thanks,
> >
> > Signed-off-by: Josef Bacik <josef@...hat.com>
> > ---
> >  man2/fallocate.2 |   15 ++++++++++++---
> >  1 files changed, 12 insertions(+), 3 deletions(-)
> >
> > diff --git a/man2/fallocate.2 b/man2/fallocate.2
> > index 42eefbd..1b28916 100644
> > --- a/man2/fallocate.2
> > +++ b/man2/fallocate.2
> > @@ -31,9 +31,8 @@ bytes.
> >
> >  The
> >  .I mode
> > -argument determines the operation to be performed on the given range.
> > -Currently only one flag is supported for
> > -.IR mode :
> > +argument determines the operation to be performed on the given range, the
> > +value can be one of the following:
> >  .TP
> >  .B FALLOC_FL_KEEP_SIZE
> >  This flag allocates and initializes to zero the disk space
> > @@ -50,6 +49,16 @@ the file size (as reported by
> >  .BR stat (2))
> >  even if it is less than
> >  .IR offset + len .
> > +.TP
> > +.B FALLOC_FL_PUNCH_HOLE
> > +This flag de-allocates the disk space within the range specified by
> > +.I offset
> > +and
> > +.IR len .
> > +This call preserves the file size (as reported by
> > +.BR stat (2)),
> > +the only change will be to the amount of space used by the file.  After a
> > +successful call, subsequent reads from this range will return 0's.
> >  .\"
> >  .\" Note from Amit Arora:
> >  .\" There were few more flags which were discussed, but none of
> > --
> > 1.6.6.1
> 
> Thanks for this patch. As noted in another mail, Lucian also sent a
> patch for FALLOC_FL_PUNCH_HOLE, and I applied his patch first, and
> then added some pieces from yours, as well as some of my own edits.
> 
> However, the addition of a second class of operation to the man page
> made it clear that some significant restructuring of the page is
> required. So I substantially reworked the page, including the
> preexisting material on the default "file allocation" operation (Dave
> C please note).
> 
> Josef, Lucian, could I ask you to check ("man -l <file>") the final
> text (below) for FALLOC_FL_PUNCH_HOLE (including the EPERM error under
> ERRORS)?
> 
> Dave, could I ask you to review my reworked text for the "Allocating
> disk space" subsection?

Looks OK to me.

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
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/