From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it, Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, selinux@vger.kernel.org,
Jan Stancek <jstancek@redhat.com>, Li Wang <liwang@redhat.com>
Subject: Re: [PATCH v4 2/4] tst_test.sh: Add TST_USR_{G,U}ID variables
Date: Thu, 18 Dec 2025 12:47:33 +0100 [thread overview]
Message-ID: <20251218114733.GA98183@pevik> (raw)
In-Reply-To: <aULQlhbHltLTbdG4@yuki.lan>
> Hi!
> > Add TST_USR_{G,U}ID variables with the default values from tst_runas.c.
> > These can be used as a default values for tests which use tst_runas and
> > need to know UID/GID for other commands.
> > It will be used in LTP IMA tests.
...
> > +# see testcases/lib/tst_runas.c
> > +export TST_USR_UID="${LTP_USR_UID:-65534}"
> > +export TST_USR_GID="${LTP_USR_GID:-65534}"
> Do we need this? We already have the default values in the C code...
I've merged the patch without notice this, therefore just to clarify.
I hoped I was clear in the commit message, obviously not.
Yes, just for a record you find the answer in the next patch:
https://lore.kernel.org/ltp/aULUsVxLIXFM19IV@yuki.lan/
So I hope everything is OK.
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: selinux@vger.kernel.org, linux-integrity@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 2/4] tst_test.sh: Add TST_USR_{G, U}ID variables
Date: Thu, 18 Dec 2025 12:47:33 +0100 [thread overview]
Message-ID: <20251218114733.GA98183@pevik> (raw)
In-Reply-To: <aULQlhbHltLTbdG4@yuki.lan>
> Hi!
> > Add TST_USR_{G,U}ID variables with the default values from tst_runas.c.
> > These can be used as a default values for tests which use tst_runas and
> > need to know UID/GID for other commands.
> > It will be used in LTP IMA tests.
...
> > +# see testcases/lib/tst_runas.c
> > +export TST_USR_UID="${LTP_USR_UID:-65534}"
> > +export TST_USR_GID="${LTP_USR_GID:-65534}"
> Do we need this? We already have the default values in the C code...
I've merged the patch without notice this, therefore just to clarify.
I hoped I was clear in the commit message, obviously not.
Yes, just for a record you find the answer in the next patch:
https://lore.kernel.org/ltp/aULUsVxLIXFM19IV@yuki.lan/
So I hope everything is OK.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-18 11:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 18:55 [PATCH v4 0/4] tst_runas.c, ima_{conditionals, measurements}.sh enhancements Petr Vorel
2025-12-09 18:55 ` [LTP] " Petr Vorel
2025-12-09 18:55 ` [PATCH v4 1/4] shell: Add tst_runas.c helper Petr Vorel
2025-12-09 18:55 ` [LTP] " Petr Vorel
2025-12-15 6:57 ` Li Wang via ltp
2025-12-17 15:13 ` Cyril Hrubis
2025-12-17 15:13 ` [LTP] " Cyril Hrubis
2025-12-17 15:57 ` Petr Vorel
2025-12-17 15:57 ` [LTP] " Petr Vorel
2025-12-09 18:55 ` [PATCH v4 2/4] tst_test.sh: Add TST_USR_{G,U}ID variables Petr Vorel
2025-12-09 18:55 ` [LTP] " Petr Vorel
2025-12-17 15:47 ` Cyril Hrubis
2025-12-17 15:47 ` [LTP] [PATCH v4 2/4] tst_test.sh: Add TST_USR_{G, U}ID variables Cyril Hrubis
2025-12-18 11:47 ` Petr Vorel [this message]
2025-12-18 11:47 ` Petr Vorel
2025-12-09 18:55 ` [PATCH v4 3/4] ima_{conditionals,measurements}.sh: Use tst_runas Petr Vorel
2025-12-09 18:55 ` [LTP] [PATCH v4 3/4] ima_{conditionals, measurements}.sh: " Petr Vorel
2025-12-17 16:05 ` [PATCH v4 3/4] ima_{conditionals,measurements}.sh: " Cyril Hrubis
2025-12-17 16:05 ` [LTP] [PATCH v4 3/4] ima_{conditionals, measurements}.sh: " Cyril Hrubis
2025-12-09 18:55 ` [PATCH v4 4/4] ima_conditionals.sh: Split test by request Petr Vorel
2025-12-09 18:55 ` [LTP] " Petr Vorel
2025-12-11 10:37 ` [LTP] [PATCH v4 0/4] tst_runas.c, ima_{conditionals, measurements}.sh enhancements Andrea Cervesato
2025-12-11 10:37 ` 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=20251218114733.GA98183@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=selinux@vger.kernel.org \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.