From: Eryu Guan <eguan@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH V2] generic/395: test GETNEXTQUOTA near INT_MAX
Date: Sat, 24 Dec 2016 18:20:11 +0800 [thread overview]
Message-ID: <20161224102011.GS1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <8c91051e-8a78-cb20-d926-ea86e5b4645a@sandeen.net>
On Wed, Dec 21, 2016 at 07:11:21PM -0600, Eric Sandeen wrote:
> XFS kernel code had a bug where GETNEXTQUOTA-type
> quotactls requesting an ID near UINT_MAX could overflow
> and return 0 as the "next" active ID.
>
> This test checks that by creating an active quota near
> UINT_MAX, then asking for the next one after it.
>
> The proper answer is ENOENT, but if we wrap we'll return
> ID 0.
>
> This also changes test-nextquota.c so that it checks
> both GETNEXTQUOTA and XGETNEXTQUOTA even if one fails;
> it stores the failure conditions and returns 1 if either
> of them fails.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> V2: cleanups from Eryu's review.
>
> Eryu - I need to send a _require_getnextquota patch, and some
> other cleanups to 244, similar to your review of this test
> (I copied this test from 244).
>
> I'll do that in reply to this patch, hopfully tonight, yet.
Thanks, Eric!
> +# remount just for kicks, make sure we get it off disk
> +_scratch_unmount
> +_qmount
> +quotaon $SCRATCH_MNT 2>/dev/null
I removed this quotaon too and merged.
Thanks,
Eryu
prev parent reply other threads:[~2016-12-24 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 15:23 [PATCH] generic/395: test GETNEXTQUOTA near INT_MAX Eric Sandeen
2016-12-20 6:25 ` Eryu Guan
2016-12-20 13:57 ` Eric Sandeen
2016-12-22 1:11 ` [PATCH V2] " Eric Sandeen
2016-12-22 1:23 ` [PATCH 1/2] generic/244: remove extra junk Eric Sandeen
2016-12-22 1:24 ` [PATCH 2/2] common: add _require_getnextquota helper Eric Sandeen
2016-12-24 10:20 ` Eryu Guan [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=20161224102011.GS1859@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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