From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 02/12] quota: Allow each filesystem to specify which quota types it supports
Date: Wed, 22 Oct 2014 18:29:15 +0200 [thread overview]
Message-ID: <20141022162915.GB18443@lst.de> (raw)
In-Reply-To: <1413902316-17997-3-git-send-email-jack@suse.cz>
On Tue, Oct 21, 2014 at 04:38:26PM +0200, Jan Kara wrote:
> Currently all filesystems supporting VFS quota support user and group
> quotas. With introduction of project quotas this is going to change so
> make sure filesystem isn't called for quota type it doesn't support by
> introduction of a bitmask determining which quota types each filesystem
> supports.
Why don't you keep this bitmask in the dquot.c instead of pushing it
to the caller? So far usage of s_dquot is mostly confined to dquot.c
(with a few leaks to the filesystems using it), so keeping it that
way seems like a good idea.
next prev parent reply other threads:[~2014-10-22 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 14:38 [Cluster-devel] [PATCH 0/12 v3] Moving i_dquot out of struct inode Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 01/12] quota: Remove const from function declarations Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 02/12] quota: Allow each filesystem to specify which quota types it supports Jan Kara
2014-10-22 16:29 ` Christoph Hellwig [this message]
2014-10-22 16:51 ` Jan Kara
2014-10-23 8:53 ` Christoph Hellwig
2014-10-21 14:38 ` [Cluster-devel] [PATCH 03/12] gfs2: Set allowed quota types Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 04/12] xfs: " Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 05/12] quota: Use function to provide i_dquot pointers Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 06/12] ext2: Convert to private i_dquot field Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 07/12] ext3: " Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 08/12] ext4: " Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 09/12] ocfs2: " Jan Kara
2014-10-23 10:25 ` Joel Becker
2014-10-23 12:05 ` Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 10/12] reiserfs: " Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 11/12] jfs: " Jan Kara
2014-10-21 14:38 ` [Cluster-devel] [PATCH 12/12] vfs: Remove i_dquot field from inode Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 11:19 [Cluster-devel] [PATCH 0/12 v4] Moving i_dquot out of struct inode Jan Kara
2014-11-04 11:19 ` [Cluster-devel] [PATCH 02/12] quota: Allow each filesystem to specify which quota types it supports 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=20141022162915.GB18443@lst.de \
--to=hch@lst.de \
/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).