From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] setpriority01: Skip only PRIO_USER when unable to add test user
Date: Tue, 19 Mar 2019 12:28:15 +0100 [thread overview]
Message-ID: <20190319112815.GA19707@dell5510> (raw)
In-Reply-To: <20190319103140.GD6204@rei>
Hi,
> > > > > I still think v1 is the right approach. But if you want TCONF for only
> > > > > for cases like Android where useradd itself isn't present, then v2 would
> > > > > be the right patch.
> > > > Agree with it, but waiting for Cyril approval to merge it.
> > > As far as I can tell this patch still removes the read-only rootfs check
> > > introduced in:
> > Good catch, eaccess check should stay in.
> > I'll put it back again and push, ok?
> Or we can check the return value 1 from useradd and map it to TCONF as
> suggested by Saravana.
Probably. According to useradd sources, exit 1 (E_PW_UPDATE) also happen when
problems to lock /etc/passwd, which could theoretically on different
circumstance than read-only /, but I guess we can ignore it.
Or we could use statvfs to detect read-only / ("can't update password file" does
can be for different purposes), but I wouldn't bother and user return value 1.
Kind regards,
Petr
[1] https://github.com/shadow-maint/shadow/blob/master/src/useradd.c#L1626
next prev parent reply other threads:[~2019-03-19 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 23:31 [LTP] [PATCH v2] setpriority01: Skip only PRIO_USER when unable to add test user Saravana Kannan
2019-03-19 8:32 ` Petr Vorel
2019-03-19 10:03 ` Cyril Hrubis
2019-03-19 10:28 ` Petr Vorel
2019-03-19 10:31 ` Cyril Hrubis
2019-03-19 11:28 ` Petr Vorel [this message]
2019-03-19 20:19 ` Saravana Kannan
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 23:28 Saravana Kannan
2019-03-07 23:31 ` Saravana Kannan
2019-03-19 8:28 ` 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=20190319112815.GA19707@dell5510 \
--to=pvorel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox