From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] syscalls/add_key05: add maxbytes/maxkeys test under unprivileged user
Date: Thu, 19 Mar 2020 12:23:32 +0100 [thread overview]
Message-ID: <20200319112332.GB440@dell5510> (raw)
In-Reply-To: <1584527574-28177-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
Hi Xu,
> This case is designed to test whether we can reach maxbytes/maxkeys
> quota exactly under unprivileged users. It is a regression test for
> commit a08bf91ce28e ("KEYS: allow reaching the keys quotas exactly").
> But this kenrel commit is a incomplete fix, it still fails on lastest
nit: typos: kenrel, lastest (will be fixed during merge).
> upstream kernel. Fix patch[1] is on linux-next branch.
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2e356101e72a
I guess this commit get's preserved when merged in mainline, so we don't have to
wait for it.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
LGTM except one concern about ltpuser setup.
> +++ b/testcases/kernel/syscalls/add_key/add_key05.c
...
> + * Test unprivileged user can support the number of keys and the
> + * number of bytes consumed in payloads of the keys. The defalut
> + * value is 200 and 20000.
> + * This is also a regresstion test for
nit: typos: defalut, regresstion (will be fixed during merge).
> + * commit a08bf91ce28e ("KEYS: allow reaching the keys quotas exactly")
> + * commit 2e356101e72a ("KEYS: reaching the keys quotas correctly")
> + */
> +struct passwd *ltpuser;
...
> +static void add_user(void)
> +{
> + if (user_added)
> + return;
> +
> + const char *const cmd_useradd[] = {"useradd", username, NULL};
> + int rc;
> +
> + switch ((rc = tst_run_cmd(cmd_useradd, NULL, NULL, 1))) {
> + case 0:
> + user_added = 1;
> + ltpuser = SAFE_GETPWNAM(username);
> + break;
> + case 1:
> + case 255:
> + break;
> + default:
> + tst_brk(TBROK, "Useradd failed (%d)", rc);
> + }
> + sprintf(fmt, "%5u: %%*5d %%*d/%%*d %%d/%%d %%d/%%d", ltpuser->pw_uid);
> +}
ltpuser is undefined for 1 and 255, therefore it gets SIGSEGV. It should either
require tst_run_cmd to exit 0 or use 0 as UID (root UID).
Kind regards,
Petr
next prev parent reply other threads:[~2020-03-19 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 13:14 [LTP] [PATCH] syscalls/add_key05: add maxbytes/maxkeys test under unprivileged user Yang Xu
2020-02-24 15:31 ` Cyril Hrubis
2020-02-26 10:19 ` Yang Xu
2020-02-28 7:00 ` Yang Xu
2020-02-28 8:47 ` [LTP] [PATCH v2] " Yang Xu
2020-03-17 12:32 ` Petr Vorel
2020-03-18 9:55 ` Yang Xu
2020-03-18 13:16 ` Petr Vorel
2020-03-18 13:17 ` Petr Vorel
2020-03-18 10:32 ` [LTP] [PATCH v3] " Yang Xu
2020-03-19 11:23 ` Petr Vorel [this message]
2020-03-20 5:15 ` Yang Xu
2020-03-20 11:50 ` Petr Vorel
2020-03-20 12:36 ` 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=20200319112332.GB440@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