From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] setreuid01.c: Rewrite using new LTP API and use TST_EXP* macros
Date: Fri, 23 Dec 2022 09:53:22 +0100 [thread overview]
Message-ID: <Y6Vsgkx/VcY/78vs@pevik> (raw)
In-Reply-To: <87ili3stt2.fsf@suse.de>
> Hello,
> Avinesh Kumar <akumar@suse.de> writes:
> > Hi,
> > I changed this simple setreuid() test to new LTP API but I think
> > this is a subset of setreuid03.c test and can be removed altogether.
> > Please share your opinion. If this should be removed, I'll post new
> > patch for that.
> Yes, I think that is reasonable.
+1. Also setreuid03.c tests as nobody, but we have no garancy setreuid01.c is
run as non-root user (it can be root or UID 1000, which has enhanced
privileges).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-23 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 7:52 [LTP] [PATCH] setreuid01.c: Rewrite using new LTP API and use TST_EXP* macros Avinesh Kumar
2022-12-22 8:47 ` Richard Palethorpe
2022-12-23 8:53 ` Petr Vorel [this message]
2023-01-09 14:55 ` Richard Palethorpe
2023-01-10 10:35 ` [LTP] [PATCH v2] " Avinesh Kumar
2023-01-10 11:12 ` Richard Palethorpe
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=Y6Vsgkx/VcY/78vs@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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 NNTP newsgroup(s).