From: Petr Vorel <pvorel@suse.cz>
To: Edward Liaw <edliaw@google.com>, Sandeep Patil <sspatil@android.com>
Cc: kernel-team@android.com, ltp@lists.linux.it
Subject: [LTP] [AOSP/Android] Better handling required user and group
Date: Mon, 2 Sep 2024 12:34:28 +0200 [thread overview]
Message-ID: <20240902103428.GB279460@pevik> (raw)
Hi Edward, Sandeep, all,
we have some long going ticket about better handling users groups in ticket #468.
I recently updated it with new proposal [1]. Then I noticed AOSP requires
SAFE_GETGRNAM_FALLBACK() [2].
I wonder how to do a proper solution in the LTP C API (which would be then
reused in LTP shell API). Could you please post what would work for AOSP
testing? (ideally to the ticket so that we keep the discussion on single place,
but it could be also here).
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/issues/468#issuecomment-2320992135
[2] https://github.com/linux-test-project/ltp/issues/468#issuecomment-2324376728
--
Mailing list info: https://lists.linux.it/listinfo/ltp
reply other threads:[~2024-09-02 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240902103428.GB279460@pevik \
--to=pvorel@suse.cz \
--cc=edliaw@google.com \
--cc=kernel-team@android.com \
--cc=ltp@lists.linux.it \
--cc=sspatil@android.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