From: Ben Myers <bpm@sgi.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/4] xfstests: Add a require_seppquota function
Date: Fri, 4 May 2012 16:26:30 -0500 [thread overview]
Message-ID: <20120504212630.GZ16881@sgi.com> (raw)
In-Reply-To: <20120221165845.23253.658.sendpatchset@chandra-lucid.austin.ibm.com>
On Tue, Feb 21, 2012 at 10:58:45AM -0600, Chandra Seetharaman wrote:
> >From 6076480613e3034eab9758903c093a0b24048658 Mon Sep 17 00:00:00 2001
> From: Chandra Seetharaman <sekharan@us.ibm.com>
> Date: Wed, 8 Feb 2012 10:04:49 -0600
> Subject: [PATCH 2/3] Add a require_seppquota function in preparation for testing
> simultaneous use of pquota and gquota in a filesystem
>
> Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
> ---
> common.quota | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/common.quota b/common.quota
> index 9736306..16344ea 100644
> --- a/common.quota
> +++ b/common.quota
> @@ -87,6 +87,15 @@ _require_nobody()
> [ $? -ne 0 ] && _notrun "group file does not contain nobody/nogroup."
> }
>
> +#
> +# checks to see if mkfs supports separate pquota
> +#
> +_require_seppquota()
> +{
> + mkfs.xfs -o test 2>&1 | grep seppquota > /dev/null
^^^^^^^
I have a nit to pick about that... FWICS there is no -o option to mkfs.xfs.
Here -o works fine to get usage only because we have not yet defined a mkfs
option for 'o'. If we were to do that at a later date... who knows?
There isn't a -h option to print usage either. It looks like the only way to
print usage so you can grep for seppquota is to do something wrong! I suggest
that you do this instead:
mkfs.xfs 2>&1 | grep seppquota > /dev/null
I think we can be fairly certain that mkfs.xfs with zero args will always be a
safe way to get usage() to kick off.
Other than that silly nit... this looks fine.
Reviewed-by: Ben Myers <bpm@sgi.com>
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-04 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 16:58 [PATCH 0/4] xfstests: Test pquota and gquota being used together Chandra Seetharaman
2012-02-21 16:58 ` [PATCH 1/4] xfstests: Fix a problem where using bsize was not working as expected Chandra Seetharaman
2012-05-04 21:01 ` Ben Myers
2012-02-21 16:58 ` [PATCH 2/4] xfstests: Add a require_seppquota function Chandra Seetharaman
2012-05-04 21:26 ` Ben Myers [this message]
2012-02-21 16:58 ` [PATCH 3/4] xfstests: Add a simple test to check separate pquota/gquota Chandra Seetharaman
2012-02-21 16:58 ` [PATCH 4/4] xfstests: Add the new test to the group file Chandra Seetharaman
2012-05-04 21:07 ` Ben Myers
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=20120504212630.GZ16881@sgi.com \
--to=bpm@sgi.com \
--cc=sekharan@us.ibm.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