From: Eric Sandeen <sandeen@sandeen.net>
To: Zorro Lang <zlang@redhat.com>, fstests@vger.kernel.org
Cc: eguan@redhat.com, sandeen@redhat.com
Subject: Re: [PATCH] xfs/133: add quota name beginning with digits test
Date: Tue, 8 Dec 2015 11:21:17 -0600 [thread overview]
Message-ID: <5667118D.2000502@sandeen.net> (raw)
In-Reply-To: <1449244857-19283-1-git-send-email-zlang@redhat.com>
On 12/4/15 10:00 AM, Zorro Lang wrote:
> There're two bugs on xfsprogs:
> 1. when a project name beinning with digits, it can't be found
> by run xfs_quota 'quota -p -v ...' command, but 'report' command
> can find it.
>
> 2. When user or group names beginning with digits, we can't
> create 'limit' for them, and can't find them either(likes above).
>
> This case will create user, group and project names which beginning
> with digits, then create limit for them, and query them.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>
> Hi,
>
> This case need a test user, that doesn't like user 'fsqa', fsqa is a
> common user for xfstests, but this case need a special and temporary
> user and group. So I create and clean them in this case.
>
> But this's the first time a xfstests case add test user/group by itself,
> so please help to review, if this's appropriate?
So, I came to the conclusion, and talking w/ Dave I think he concurs, that it
would be better to document the need for these users in the README; then,
just like the "fsgqa" user, your test can check for the existence of i.e.
a "123456-fsgqa" user, and simply _notrun() if it's not present. This way
/etc/passwd stays under the system administrator's control, but it's clear why
the test is skipped if the user doesn't exist.
-Eric
next prev parent reply other threads:[~2015-12-08 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 16:00 [PATCH] xfs/133: add quota name beginning with digits test Zorro Lang
2015-12-08 17:21 ` Eric Sandeen [this message]
2015-12-09 2:43 ` Zirong Lang
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=5667118D.2000502@sandeen.net \
--to=sandeen@sandeen.net \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=zlang@redhat.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