From: Petr Vorel <pvorel@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>,
Cyril Hrubis <chrubis@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3 0/2] mount03: Convert to new API
Date: Tue, 16 Aug 2022 13:49:54 +0200 [thread overview]
Message-ID: <YvuEYiIq23D6/zw6@pevik> (raw)
In-Reply-To: <f7c6df02-3c39-ead8-2bbd-8cc26d36ff7f@fujitsu.com>
Hi Xu,
...
> > +++ testcases/kernel/syscalls/mount/mount03.c
...
> > #define FILE_MODE 0644
> > #define SUID_MODE 0511
Good catch, SUID_MODE must be 04511.
> Here SUID_MODE miss S_ISUID, that is why this case also pass if we
> execute a program on filesystem that not mounted with nosuid option.
@Cyril any idea what's wrong here? (not yet tested on tst_reinit()).
> Also, it seems make check code has problem when detecting S_ISUID
Indeed.
> Symbolic permissions 'S_IRUSR|S_IXUSR|S_IXGRP|S_IXOTH' are not
> preferred. Consider using octal permissions '0511'.
This already been implemented.
> Since we have converted mount03 into new api, mount03_setuid_test.c
> should also be converted into new spdx.
Planning to, with other required fixes (C API pointed out by Cyril).
> Best Regards
> Yang Xu
> > @@ -74,12 +75,18 @@ static void test_nosuid(void)
> > {
> > pid_t pid;
> > int status;
> > + struct stat st;
> > +
> > + SAFE_CP(TESTBIN, BIN_PATH);
> > + SAFE_STAT(BIN_PATH, &st);
> > + if (st.st_mode != SUID_MODE)
> > + SAFE_CHMOD(BIN_PATH, SUID_MODE);
> > pid = SAFE_FORK();
> > if (!pid) {
> > SAFE_SETGID(nobody_gid);
> > SAFE_SETREUID(-1, nobody_uid);
> > - SAFE_EXECLP(TESTBIN, TESTBIN, NULL);
> > + SAFE_EXECL(BIN_PATH, TESTBIN, NULL);
> > }
> > SAFE_WAITPID(pid, &status, 0);
> > @@ -137,18 +144,10 @@ static struct tcase {
> > static void setup(void)
> > {
> > - struct stat st;
> > struct passwd *ltpuser = SAFE_GETPWNAM("nobody");
> > nobody_uid = ltpuser->pw_uid;
> > nobody_gid = ltpuser->pw_gid;
> > -
> > - snprintf(file, PATH_MAX, "%s/%s", MNTPOINT, TESTBIN);
> > - SAFE_CP(TESTBIN, file);
> > -
> > - SAFE_STAT(file, &st);
> > - if (st.st_mode != SUID_MODE)
> > - SAFE_CHMOD(file, SUID_MODE);
> > }
> > static void cleanup(void)
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-16 11:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 13:57 [LTP] [PATCH v3 0/2] mount03: Convert to new API Petr Vorel
2022-08-11 13:57 ` [LTP] [PATCH v3 1/2] tst_test_macros.h: Add TST_EXP_EQ_STR Petr Vorel
2022-08-15 3:17 ` xuyang2018.jy
2022-08-11 13:57 ` [LTP] [PATCH v3 2/2] mount03: Convert to new API Petr Vorel
2022-08-16 9:07 ` Cyril Hrubis
2022-08-16 9:18 ` Petr Vorel
2022-08-16 9:31 ` Cyril Hrubis
2022-08-15 5:15 ` [LTP] [PATCH v3 0/2] " xuyang2018.jy
2022-08-15 6:40 ` Petr Vorel
2022-08-15 6:58 ` xuyang2018.jy
2022-08-15 8:28 ` Petr Vorel
2022-08-15 9:57 ` xuyang2018.jy
2022-08-15 14:19 ` Petr Vorel
2022-08-16 3:40 ` xuyang2018.jy
2022-08-16 11:49 ` Petr Vorel [this message]
2022-08-16 13:01 ` Petr Vorel
2022-08-17 2:23 ` xuyang2018.jy
2022-08-22 13:28 ` Petr Vorel
2022-08-22 13:35 ` Petr Vorel
2022-08-16 4:37 ` xuyang2018.jy
2022-08-16 6:57 ` Petr Vorel
2022-08-16 7:28 ` xuyang2018.jy
2022-08-16 9:00 ` Cyril Hrubis
2022-08-16 9:06 ` Petr Vorel
2022-08-16 9:57 ` xuyang2018.jy
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=YvuEYiIq23D6/zw6@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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