From: Richard Weinberger <richard@nod.at>
To: fstests@vger.kernel.org
Subject: fsgqa group membership?
Date: Sun, 14 Jan 2024 16:42:41 +0100 (CET) [thread overview]
Message-ID: <1998649210.233983.1705246961955.JavaMail.zimbra@nod.at> (raw)
Hi!
After migrating to a new test environment, I observed that generic/193 failed.
Initially, I assumed it was a UBIFS regression, but it appears that all other file systems have also been affected.
generic/193 - output mismatch (see /root/xfstests-dev/results//generic/193.out.bad)
--- tests/generic/193.out 2024-01-14 08:55:20.114082471 +0000
+++ /root/xfstests-dev/results//generic/193.out.bad 2024-01-14 14:30:51.598725128 +0000
@@ -45,10 +45,10 @@
check that suid/sgid bits are cleared after successful truncate...
with no exec perm
before: -rwSr-Sr--
-after: -rw-r-Sr--
+after: -rw-r--r--
with user exec perm
before: -rwsr-Sr--
...
(Run 'diff -u /root/xfstests-dev/tests/generic/193.out /root/xfstests-dev/results//generic/193.out.bad' to see the entire diff)
It turned out that the test failed because the user "fsgqa" did not have the "fsgqa" group assigned.
After rectifying this, the test passed successfully.
But it is nowhere stated that this has to be that way.
README says only:
6. (optional) Create fsgqa test users and groups:
$ sudo useradd -m fsgqa
$ sudo useradd 123456-fsgqa
$ sudo useradd fsgqa2
$ sudo groupadd fsgqa
Just in case, users fsgqa and fsgqa2 want the groups fsgqa/fsgqa2 as their primary groups
to have all tests work as expected?
Thanks,
//richard
next reply other threads:[~2024-01-14 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 15:42 Richard Weinberger [this message]
2024-01-14 20:18 ` fsgqa group membership? Zorro Lang
2024-01-14 20:48 ` Richard Weinberger
2024-01-15 2:58 ` Zorro Lang
2024-01-15 2:57 ` Theodore Ts'o
2024-01-15 21:28 ` Richard Weinberger
2024-01-16 16:26 ` Zorro 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=1998649210.233983.1705246961955.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=fstests@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).