cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 03/12] xfs: Set allowed quota types
Date: Tue, 7 Oct 2014 21:29:35 +0200	[thread overview]
Message-ID: <20141007192935.GF30038@quack.suse.cz> (raw)
In-Reply-To: <20141006203028.GB2301@dastard>

On Tue 07-10-14 07:30:28, Dave Chinner wrote:
> On Wed, Oct 01, 2014 at 09:31:25PM +0200, Jan Kara wrote:
> > We support user, group, and project quotas. Tell VFS about it.
> > 
> > CC: xfs at oss.sgi.com
> > CC: Dave Chinner <david@fromorbit.com>
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> >  fs/xfs/xfs_super.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> > index b194652033cd..b32e998e8cbc 100644
> > --- a/fs/xfs/xfs_super.c
> > +++ b/fs/xfs/xfs_super.c
> > @@ -1419,6 +1419,8 @@ xfs_fs_fill_super(
> >  	sb->s_export_op = &xfs_export_operations;
> >  #ifdef CONFIG_XFS_QUOTA
> >  	sb->s_qcop = &xfs_quotactl_operations;
> > +	sb->s_dquot.allowed_types = (1 << USRQUOTA) | (1 << GRPQUOTA) |
> > +				    (1 << PRJQUOTA);
> 
> Would it be better to define masks for these rather than open
> coding these shifts everywhere?
  I can do that. Any suggestion for a name? I was thinking about it for a
while and couldn't come up with anything satisfactory...

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR



  reply	other threads:[~2014-10-07 19:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 19:31 [Cluster-devel] [PATCH 0/12 RFC] Moving i_dquot out of struct inode Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 01/12] quota: Allow each filesystem to specify which quota types it supports Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 02/12] gfs2: Set allowed quota types Jan Kara
2014-10-02 10:41   ` Steven Whitehouse
2014-10-01 19:31 ` [Cluster-devel] [PATCH 03/12] xfs: " Jan Kara
2014-10-06 20:30   ` Dave Chinner
2014-10-07 19:29     ` Jan Kara [this message]
2014-10-07 19:46       ` Andreas Dilger
2014-10-08  8:42         ` Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 04/12] fs: Generic infrastructure for optional inode fields Jan Kara
2014-10-01 21:05   ` Andreas Dilger
2014-10-08  8:45     ` Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 05/12] quota: Use optional inode field for i_dquot pointers Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 06/12] ext2: Convert to private i_dquot field Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 07/12] ext3: " Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 08/12] ext4: " Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 09/12] ocfs2: " Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 10/12] reiserfs: " Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 11/12] jfs: " Jan Kara
2014-10-01 19:31 ` [Cluster-devel] [PATCH 12/12] vfs: Remove i_dquot field from inode Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2014-10-10 14:54 [Cluster-devel] [PATCH 0/12 v2] Moving i_dquot out of struct inode Jan Kara
2014-10-10 14:55 ` [Cluster-devel] [PATCH 03/12] xfs: Set allowed quota types 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=20141007192935.GF30038@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).