From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] 'nobody' user for testing
Date: Thu, 16 Oct 2025 15:09:52 +0200 [thread overview]
Message-ID: <20251016130952.GA281409@pevik> (raw)
In-Reply-To: <aPDlzuox-54oxTtp@yuki.lan>
> Hi!
> > Short term solution will be Jan's suggestion to write simple "sudo" binary or
> > even just let testers to fix the setup (i.e. fix it for us in openQA).
> I guess that having a small helper to execute commands as a selected
> user would be reasonable. We already have tst_sleep because the sleep
> commands in different shells behaves differently.
> Adding tst_sudo that would take an user and command to execute does make
> sense here I suppose.
OK, I can write it unless Jan plans to work on it (Jan, please let me know).
I propose to have the usual LTP approach to have functionality used by C API
(e.g. lib/tst_sudo.c) and reused by thin wrapper available for shell API
(testcases/lib/tst_sudo.c).
Few C API tests would use it (prctl06 and other mentioned previously [1] as 3)),
in shell API only these 2 IMA tests.
> And I think that the question if we need a separate user for LTP testing is
> orthogonal.
Agree. I just brought these two topics together as they are related.
So, as a separate topic/effort, do you see any room for C API functions for 1)
and 2) in [1]?
Kind regards,
Petr
[1] https://lore.kernel.org/ltp/20251006094837.GC66983@pevik/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-16 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:27 [LTP] [RFC] 'nobody' user for testing Petr Vorel
2025-09-22 8:48 ` Jan Stancek via ltp
2025-09-26 12:25 ` Petr Vorel
2025-10-06 9:48 ` Petr Vorel
2025-09-26 13:24 ` Andrea Cervesato via ltp
2025-09-29 8:31 ` Petr Vorel
2025-10-16 12:32 ` Cyril Hrubis
2025-10-16 13:09 ` Petr Vorel [this message]
2025-10-16 13:35 ` Cyril Hrubis
2025-10-16 14:07 ` Petr Vorel
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=20251016130952.GA281409@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.