From: Jan Kara <jack@suse.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/6] fs: add hole punching to fallocate
Date: Fri, 19 Nov 2010 00:43:31 +0100 [thread overview]
Message-ID: <20101118234331.GD5004@quack.suse.cz> (raw)
In-Reply-To: <1290044780-2902-2-git-send-email-josef@redhat.com>
On Wed 17-11-10 20:46:15, Josef Bacik wrote:
> Hole punching has already been implemented by XFS and OCFS2, and has the
> potential to be implemented on both BTRFS and EXT4 so we need a generic way to
> get to this feature. The simplest way in my mind is to add FALLOC_FL_PUNCH_HOLE
> to fallocate() since it already looks like the normal fallocate() operation.
> I've tested this patch with XFS and BTRFS to make sure XFS did what it's
> supposed to do and that BTRFS failed like it was supposed to. Thank you,
Looks nice now. Acked-by: Jan Kara <jack@suse.cz>
Honza
>
> Signed-off-by: Josef Bacik <josef@redhat.com>
> ---
> fs/open.c | 7 ++++++-
> include/linux/falloc.h | 1 +
> 2 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/fs/open.c b/fs/open.c
> index 4197b9e..5b6ef7e 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -223,7 +223,12 @@ int do_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
> return -EINVAL;
>
> /* Return error if mode is not supported */
> - if (mode && !(mode & FALLOC_FL_KEEP_SIZE))
> + if (mode & ~(FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE))
> + return -EOPNOTSUPP;
> +
> + /* Punch hole must have keep size set */
> + if ((mode & FALLOC_FL_PUNCH_HOLE) &&
> + !(mode & FALLOC_FL_KEEP_SIZE))
> return -EOPNOTSUPP;
>
> if (!(file->f_mode & FMODE_WRITE))
> diff --git a/include/linux/falloc.h b/include/linux/falloc.h
> index 3c15510..73e0b62 100644
> --- a/include/linux/falloc.h
> +++ b/include/linux/falloc.h
> @@ -2,6 +2,7 @@
> #define _FALLOC_H_
>
> #define FALLOC_FL_KEEP_SIZE 0x01 /* default is extend size */
> +#define FALLOC_FL_PUNCH_HOLE 0x02 /* de-allocates range */
>
> #ifdef __KERNEL__
>
> --
> 1.6.6.1
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next parent reply other threads:[~2010-11-18 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290044780-2902-1-git-send-email-josef@redhat.com>
[not found] ` <1290044780-2902-2-git-send-email-josef@redhat.com>
2010-11-18 23:43 ` Jan Kara [this message]
[not found] <1289840723-3056-1-git-send-email-josef@redhat.com>
[not found] ` <1289840723-3056-2-git-send-email-josef@redhat.com>
2010-11-16 11:16 ` [Cluster-devel] [PATCH 1/6] fs: add hole punching to fallocate Jan Kara
2010-11-16 11:43 ` Jan Kara
[not found] ` <20101116125249.GB31957@dhcp231-156.rdu.redhat.com>
2010-11-16 13:14 ` Jan Kara
[not found] <1289248327-16308-1-git-send-email-josef@redhat.com>
[not found] ` <20101109011222.GD2715@dastard>
[not found] ` <20101109033038.GF3099@thunk.org>
[not found] ` <20101109044242.GH2715@dastard>
[not found] ` <20101109214147.GK3099@thunk.org>
2010-11-09 21:53 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101118234331.GD5004@quack.suse.cz \
--to=jack@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).