From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] gfs2: Don't support fallocate on jdata files
Date: Tue, 9 Jun 2015 10:19:33 -0400 (EDT) [thread overview]
Message-ID: <1989745871.13423209.1433859573419.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1433367046-65230-1-git-send-email-adas@redhat.com>
----- Original Message -----
> We cannot provide an efficient implementation due to the headers
> on the data blocks, so there doesn't seem much point in having it.
>
> Resolves: rhbz#1221331
> Signed-off-by: Abhi Das <adas@redhat.com>
> ---
> fs/gfs2/file.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> index c706c6d..8252115 100644
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@ -917,7 +917,7 @@ static long gfs2_fallocate(struct file *file, int mode,
> loff_t offset, loff_t le
> struct gfs2_holder gh;
> int ret;
>
> - if (mode & ~FALLOC_FL_KEEP_SIZE)
> + if ((mode & ~FALLOC_FL_KEEP_SIZE) || gfs2_is_jdata(ip))
> return -EOPNOTSUPP;
>
> mutex_lock(&inode->i_mutex);
> --
> 1.8.1.4
>
>
Hi,
Now that all the questions have been answered, I pushed this patch to the
for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=86066914edff2316cbed63aac8a87d5001441a16
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2015-06-09 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 21:30 [Cluster-devel] [GFS2 PATCH] gfs2: Don't support fallocate on jdata files Abhi Das
2015-06-04 8:42 ` Steven Whitehouse
2015-06-04 10:27 ` Andrew Price
2015-06-04 10:36 ` Steven Whitehouse
2015-06-09 14:19 ` Bob Peterson [this message]
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=1989745871.13423209.1433859573419.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
/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).