From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] quota: Add support for ->get_nextdqblk() for VFS quota
Date: Fri, 19 Feb 2016 12:43:13 -0600 [thread overview]
Message-ID: <56C76241.9020203@sandeen.net> (raw)
In-Reply-To: <20160219183342.GH30068@quack.suse.cz>
On 2/19/16 12:33 PM, Jan Kara wrote:
> On Fri 19-02-16 11:31:58, Eric Sandeen wrote:
>>
>>
>> On 2/4/16 8:28 AM, Jan Kara wrote:
>>> Add infrastructure for supporting get_nextdqblk() callback for VFS
>>> quotas. Translate the operation into a callback to appropriate
>>> filesystem and consequently to quota format callback.
>>>
>>> Signed-off-by: Jan Kara <jack@suse.cz>
>>> ---
>>> fs/ext4/super.c | 1 +
>>> fs/quota/dquot.c | 39 +++++++++++++++++++++++++++++++++++++++
>>> fs/reiserfs/super.c | 1 +
>>> include/linux/quota.h | 3 +++
>>> include/linux/quotaops.h | 3 +++
>>> 5 files changed, 47 insertions(+)
>>>
>>> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
>>> index f1b56ff01208..51649f442bf6 100644
>>> --- a/fs/ext4/super.c
>>> +++ b/fs/ext4/super.c
>>> @@ -1100,6 +1100,7 @@ static const struct dquot_operations ext4_quota_operations = {
>>> .write_info = ext4_write_info,
>>> .alloc_dquot = dquot_alloc,
>>> .destroy_dquot = dquot_destroy,
>>> + .get_next_id = dquot_get_next_id,
>>> };
>>
>> Hi Jan, doesn't this also need to set:
>>
>>
>> + .get_nextdqblk = dquot_get_next_dqblk,
>>
>> in ext4_qctl_sysfile_operations?
>
> Indeed, thanks for catching this. Patch added (with your authorship and
> sign-off) into my tree and this time I've properly tested Q_GETNEXTQUOTA
> for ext4 with quota in hidden inodes indeed works (previously I've tested
> only visible quota files).
Thanks Jan, I wasn't quite sure what it should be doing, but this seemed
right. ;) Sorry for not sending a proper patch.
So, when you tested visible quota files, I assume it was just falling
back to the non-next variants of the quotactl, right? We should not
be hooking up the call for the visible quota files, right?
FWIW, there is a test in [x]fstests now for the [X]GETNEXT calls, it's
generic/244
Thanks!
-Eric
> Honza
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-19 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:28 [PATCH 0/3 v2] Q_GETNEXTQUOTA support Jan Kara
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 [this message]
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=56C76241.9020203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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