From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: "Pu Lehui" <pulehui@huaweicloud.com>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Björn Töpel" <bjorn@kernel.org>,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Puranjay Mohan <puranjay@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>, Pu Lehui <pulehui@huawei.com>
Subject: Re: [PATCH bpf-next 3/5] selftests/bpf: Use /tmp for temporary file in d_path
Date: Tue, 6 Oct 2026 10:09:32 -0700 [thread overview]
Message-ID: <501b9da8-bc0c-4c02-866d-f50b20b60289@linux.dev> (raw)
In-Reply-To: <b5f31057-e2e3-4c73-8edb-c8e70960a319@linux.dev>
On 10/5/26 3:54 PM, Ihor Solodrai wrote:
> On 9/29/26 11:24 PM, Pu Lehui wrote:
>>
>> On 2026/9/30 0:29, Alexei Starovoitov wrote:
>>> On Tue, Sep 29, 2026 at 08:39 AM Pu Lehui <pulehui@huaweicloud.com> wrote:
>>>> The failure occurs because the rootfs created by libbpf/ci [0] does not
>>>> mount /dev/shm, causing temporary file creation under /dev/shm to fail.
>>>>
>>>> Let's switch to using /tmp instead to fix this issue.
>>>
>>> This will break BPF CI.
>>> The test was using /tmp up to v4 and was moved to /dev/shm in v5,
>>> since /tmp is on 9p in BPF CI and 9p doesn't support fallocate. See
>>> https://lore.kernel.org/all/20251206141210.3148-1-electronlsr@gmail.com/
>>> vmtest's init mounts tmpfs at /dev/shm, /run and /mnt, but not at /tmp.
>>> So fallocate() will return EOPNOTSUPP and d_path/check_mem_access
>>> will fail on x86, arm64 and s390.
>>>
>>> Mount tmpfs at /dev/shm in mkrootfs_tweak.sh like you did for /tmp in [1]
>>> and drop this patch.
>>>
>>> pw-bot: cr
>>
>> Hi Alexei and Ihor,
>>
>> I have been make a pr for mount tmpfs at /dev/shm, pls take a look.
>>
>> https://github.com/libbpf/ci/pull/239
>
>
> Merged, thanks.
Pu Lehui,
I just realized that this change may not be enough.
If you want to make sure the selftests will run properly in BPF CI,
please try the vmtest tool (a qemu wrapper):
https://github.com/danobi/vmtest
You should be able to run riscv64 in emulation through it.
next prev parent reply other threads:[~2026-10-06 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 8:39 [PATCH bpf-next 0/5] riscv, bpf: Prepare for upcoming daily CI Pu Lehui
2026-09-29 8:39 ` [PATCH bpf-next 1/5] bpf, riscv: Fix stack-passed arguments for indirect trampolines Pu Lehui
2026-09-29 16:28 ` Alexei Starovoitov
2026-09-29 8:39 ` [PATCH bpf-next 2/5] selftests/bpf: Set CONFIG_HZ_100 for riscv64 Pu Lehui
2026-09-29 16:29 ` Alexei Starovoitov
2026-09-29 8:39 ` [PATCH bpf-next 3/5] selftests/bpf: Use /tmp for temporary file in d_path Pu Lehui
2026-09-29 16:29 ` Alexei Starovoitov
2026-09-30 6:24 ` Pu Lehui
2026-10-05 22:54 ` Ihor Solodrai
2026-10-06 17:09 ` Ihor Solodrai [this message]
2026-09-29 8:39 ` [PATCH bpf-next 4/5] selftests/bpf: Update qemu config for riscv64 in vmtest.sh Pu Lehui
2026-09-29 8:39 ` [PATCH bpf-next 5/5] selftests/bpf: Update DENYLIST.riscv64 Pu Lehui
2026-09-29 16:29 ` Alexei Starovoitov
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=501b9da8-bc0c-4c02-866d-f50b20b60289@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=alex@ghiti.fr \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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®