From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [PATCH 3/7] quota: add new quotactl Q_GETNEXTQUOTA
Date: Fri, 22 Jan 2016 07:58:56 -0600 [thread overview]
Message-ID: <56A235A0.7060100@sandeen.net> (raw)
In-Reply-To: <20160122092822.GC16898@quack.suse.cz>
On 1/22/16 3:28 AM, Jan Kara wrote:
> On Thu 21-01-16 22:07:20, Eric Sandeen wrote:
...
> Same comments as for XFS version apply here.
*nod*
> Furthermore:
>
>> diff --git a/fs/quota/compat.c b/fs/quota/compat.c
>> index fb1892f..80773a4 100644
>> --- a/fs/quota/compat.c
>> +++ b/fs/quota/compat.c
>> @@ -19,6 +19,19 @@ struct compat_if_dqblk {
>> compat_uint_t dqb_valid;
>> };
>>
>> +struct compat_if_nextdqblk {
>> + compat_u64 dqb_bhardlimit;
>> + compat_u64 dqb_bsoftlimit;
>> + compat_u64 dqb_curspace;
>> + compat_u64 dqb_ihardlimit;
>> + compat_u64 dqb_isoftlimit;
>> + compat_u64 dqb_curinodes;
>> + compat_u64 dqb_btime;
>> + compat_u64 dqb_itime;
>> + compat_uint_t dqb_valid;
>> + compat_uint_t dqb_id;
>> +};
>> +
>
> Is there a need for compat version of this structure? Everything is
> naturally aligned and the size is a multiple of 8 bytes. But these things
> keep surprising me... Added CC to linux-api in a hope that there's someone
> who definitely knows.
Ok, yeah, I wasn't sure. I'll take all the compat stuff out of this one,
and can do a separate patch if needed, but I bet you're right, it's probably
not. I did set up to test 32-compat calls, so I'll just test w/o this.
I'd be perfectly happy to drop it. :)
Thanks for the review, Jan.
-Eric
prev parent reply other threads:[~2016-01-22 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453435644-32261-1-git-send-email-sandeen@redhat.com>
[not found] ` <1453435644-32261-4-git-send-email-sandeen@redhat.com>
2016-01-22 9:28 ` [PATCH 3/7] quota: add new quotactl Q_GETNEXTQUOTA Jan Kara
2016-01-22 13:58 ` Eric Sandeen [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=56A235A0.7060100@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).