From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Cyril Hrubis" <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 05/13] vma05.sh, keyctl01.sh: Add groups
Date: Wed, 24 Jun 2026 11:14:14 +0000 [thread overview]
Message-ID: <6a3bbc07.f844783c.da03b.06a9@mx.google.com> (raw)
In-Reply-To: <aju2jwCz8aky9FgR@yuki.lan>
> Hi!
> > as I already mentioned, I think we should do this in all tests,
> > instead of having it only for shell tests. I know manual groups
> > are error-prone, but they give us good control over what we are
> > setting up.
> >
> > I'm not sure if adding groups based on folders as we decided to
> > do it for C API is a good idea. A tst_test->groups array feels
> > better suited, if shell tests can't automatically support the
> > same approach.
>
> I fear that we will have a lot of typos and wrong data in there. We had
> quite a few wrong CVE tags already, because we weren't checking them for
> validity.
>
> I'm okay with this as long as we have a checks in 'make check' that make
> sure that the manually assigned groups are correct. For that we would
> need the same heuristic we have for automatic groups to check that we
> didn't miss anything and a list of valid groups to check againts to
> guard againts typos.
Don't forget we also have the agent that works quite good on these
small tasks. We can add a rule and make sure they are always valid
groups.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-24 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260624091900.4107041-6-chrubis@suse.cz>
2026-06-24 10:42 ` [LTP] [PATCH 05/13] vma05.sh, keyctl01.sh: Add groups Andrea Cervesato via ltp
2026-06-24 10:50 ` Cyril Hrubis
2026-06-24 11:10 ` Cyril Hrubis
2026-06-24 11:14 ` Andrea Cervesato via ltp [this message]
2026-06-24 12:28 ` Cyril Hrubis
2026-06-24 12:37 ` Andrea Cervesato via ltp
2026-06-24 13:21 ` Cyril Hrubis
2026-06-24 13:25 ` Andrea Cervesato via ltp
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=6a3bbc07.f844783c.da03b.06a9@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@suse.cz \
/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