From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] gfs2: allow userspace to set GFS2_DIF_SYSTEM using FS_RESERVED_FL
Date: Tue, 27 Oct 2015 11:18:15 +0000 [thread overview]
Message-ID: <562F5D77.8080402@redhat.com> (raw)
In-Reply-To: <1445638867-30814-1-git-send-email-adas@redhat.com>
Hi,
I'm not sure that is a good idea, since it is possible that someone else
might find a use for that flag. Can we not simply set the
GFS2_DIF_SYSTEM flag on any inode that is created via the metafs? That
would resolve the issue without having to have a new interface I think,
Steve.
On 23/10/15 23:21, Abhi Das wrote:
> Repurpose the existing VFS FS_RESERVED_FL flag to set GFS2_DIF_SYSTEM
> using the FS_IOC_SETFLAGS ioctl.
>
> Resolves: rhbz#1272086
> Signed-off-by: Abhi Das <adas@redhat.com>
> ---
> fs/gfs2/file.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> index 71cd138..ead0d0a 100644
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@ -137,6 +137,7 @@ static const u32 fsflags_to_gfs2[32] = {
> [12] = GFS2_DIF_EXHASH,
> [14] = GFS2_DIF_INHERIT_JDATA,
> [17] = GFS2_DIF_TOPDIR,
> + [31] = GFS2_DIF_SYSTEM,
> };
>
> static const u32 gfs2_to_fsflags[32] = {
> @@ -147,6 +148,7 @@ static const u32 gfs2_to_fsflags[32] = {
> [gfs2fl_ExHash] = FS_INDEX_FL,
> [gfs2fl_TopLevel] = FS_TOPDIR_FL,
> [gfs2fl_InheritJdata] = FS_JOURNAL_DATA_FL,
> + [gfs2fl_System] = FS_RESERVED_FL,
> };
>
> static int gfs2_get_flags(struct file *filp, u32 __user *ptr)
prev parent reply other threads:[~2015-10-27 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 22:21 [Cluster-devel] [GFS2 PATCH] gfs2: allow userspace to set GFS2_DIF_SYSTEM using FS_RESERVED_FL Abhi Das
2015-10-23 22:21 ` [Cluster-devel] [GFS2] gfs2-utils: make gfs2_jadd set GFS2_DIF_SYSTEM flag on system inodes Abhi Das
2015-10-27 11:18 ` Steven Whitehouse [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=562F5D77.8080402@redhat.com \
--to=swhiteho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.