From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: w@1wt.eu, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 11/15] selftests/nolibc: prepare /tmp for tmpfs or ramfs
Date: Fri, 30 Jun 2023 10:32:41 +0200 [thread overview]
Message-ID: <457759dc-cd95-4474-a184-242bdb028445@t-8ch.de> (raw)
In-Reply-To: <9dc032064dde254a03e2111da1e58344deca6522.1688078605.git.falcon@tinylab.org>
On 2023-06-30 07:52:03+0800, Zhangjin Wu wrote:
> Let's create a /tmp directory and mount tmpfs there, if tmpfs is not
> mountable, use ramfs as tmpfs.
>
> tmpfs will be used instead of procfs for some tests.
>
> Signed-off-by: Zhangjin Wu <falcon@tinylab.org>
> ---
> tools/testing/selftests/nolibc/nolibc-test.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
> index c0f5302ada5d..8e3e2792f5e3 100644
> --- a/tools/testing/selftests/nolibc/nolibc-test.c
> +++ b/tools/testing/selftests/nolibc/nolibc-test.c
> @@ -1054,6 +1054,10 @@ int prepare(void)
> }
> }
>
> + /* try to mount /tmp if not mounted, if not mountable, use ramfs as tmpfs */
> + if (stat("/tmp/.", &stat_buf) == 0 || mkdir("/tmp", 0755) == 0)
> + mount("none", "/tmp", "tmpfs", 0, 0);
> +
mkdir()
mount()
without any error checking should do the same and be easier to read.
> return 0;
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-06-30 8:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 23:22 [PATCH v2 00/15] allow run with minimal kernel config Zhangjin Wu
2023-06-29 23:23 ` [PATCH v2 01/15] selftests/nolibc: stat_fault: silence NULL argument warning with glibc Zhangjin Wu
2023-06-29 23:25 ` [PATCH v2 02/15] selftests/nolibc: gettid: restore for glibc and musl Zhangjin Wu
2023-06-29 23:26 ` [PATCH v2 03/15] selftests/nolibc: add _LARGEFILE64_SOURCE for musl Zhangjin Wu
2023-06-29 23:28 ` [PATCH v2 04/15] selftests/nolibc: fix up int_fast16/32_t test cases " Zhangjin Wu
2023-06-29 23:29 ` [PATCH v2 05/15] selftests/nolibc: fix up kernel parameters support Zhangjin Wu
2023-06-29 23:31 ` [PATCH v2 06/15] selftests/nolibc: stat_timestamps: remove procfs dependency Zhangjin Wu
2023-06-29 23:37 ` [PATCH v2 07/15] selftests/nolibc: link_cross: use /proc/self/cmdline Zhangjin Wu
2023-06-29 23:45 ` [PATCH v2 08/15] tools/nolibc: add rmdir() support Zhangjin Wu
2023-06-29 23:48 ` [PATCH v2 09/15] selftests/nolibc: add a new rmdir() test case Zhangjin Wu
2023-06-29 23:49 ` [PATCH v2 10/15] selftests/nolibc: fix up failures when CONFIG_PROC_FS=n Zhangjin Wu
2023-06-29 23:52 ` [PATCH v2 11/15] selftests/nolibc: prepare /tmp for tmpfs or ramfs Zhangjin Wu
2023-06-30 8:32 ` Thomas Weißschuh [this message]
2023-06-30 10:18 ` Zhangjin Wu
2023-06-29 23:54 ` [PATCH v2 12/15] selftests/nolibc: add common get_tmpfile() Zhangjin Wu
2023-06-30 0:00 ` [PATCH v2 13/15] selftests/nolibc: rename chroot_exe to chroot_tmpfile Zhangjin Wu
2023-06-30 8:45 ` Thomas Weißschuh
2023-06-30 11:14 ` Zhangjin Wu
2023-06-30 0:01 ` [PATCH v2 14/15] selftests/nolibc: add chmod_tmpfile test Zhangjin Wu
2023-06-30 0:03 ` [PATCH v2 15/15] selftests/nolibc: vfprintf: remove MEMFD_CREATE dependency Zhangjin Wu
2023-06-30 8:50 ` [PATCH v2 00/15] allow run with minimal kernel config Thomas Weißschuh
2023-06-30 12:04 ` Zhangjin Wu
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=457759dc-cd95-4474-a184-242bdb028445@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®