From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Mark Fasheh <mfasheh@suse.com>, Jan Kara <jack@suse.cz>,
Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com
Subject: [PATCH 0/3 v2] Q_GETNEXTQUOTA support
Date: Thu, 4 Feb 2016 15:28:04 +0100 [thread overview]
Message-ID: <1454596087-6814-1-git-send-email-jack@suse.cz> (raw)
Hello,
the patch set below adds support for VFS quotas for Q_GETNEXTQUOTA quotactl
and thus repquota(8) doesn't have to iterate over /etc/passwd or LDAP database
to report all quota limits. ext2, ext4, reiserfs, jfs, and ocfs2 support this
quotactl (and Q_XGETNEXTQUOTA as well) after applying this patch set. XFS
bits will likely get merged independently through XFS tree. If nobody objects,
I'll push these patches to my tree in a few days.
Changes since v2:
* Added get_next_id() operation to dquot_operations to allow for cleaner
support in OCFS2
* Added OCFS2 support
Honza
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-04 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:28 Jan Kara [this message]
2016-02-04 14:28 ` [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota Jan Kara
2016-02-05 1:05 ` Dave Chinner
2016-02-08 6:15 ` Dave Chinner
2016-02-08 14:27 ` Jan Kara
2016-02-08 14:34 ` Jan Kara
2016-02-19 17:31 ` Eric Sandeen
2016-02-19 18:33 ` Jan Kara
2016-02-19 18:43 ` Eric Sandeen
2016-02-22 8:01 ` Jan Kara
2016-02-04 14:28 ` [PATCH 2/3] quota_v2: Implement get_next_id() for V2 quota format Jan Kara
2016-02-04 14:28 ` [PATCH 3/3] ocfs2: Implement get_next_id() 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=1454596087-6814-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=xfs@oss.sgi.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