Hi Jakub, Matt, On Thu, 2026-01-15 at 18:49 -0800, Jakub Kicinski wrote: > On Thu, 15 Jan 2026 17:02:40 +0800 Geliang Tang wrote: > > This is because the /tmp directory uses the virtiofs filesystem, > > which does > > not support the O_TMPFILE feature. > > I don't think selftests are expected to support setups where /tmp > isn't tmp. Please fix your setup instead (or explain why it's very
Thanks for reviewing. I recently implemented TLS support for MPTCP and have been adding MPTCP test items to the TLS selftests. When running these in the MPTCP upstream CI (mptcp-upstream-virtme-docker), these O_TMPFILE unsupported errors occurred. Following your suggestion, I looked into the mptcp-upstream-virtme- docker configuration and found that /tmp isn't mounted as tmpfs; it's just a plain directory. I've opened a PR to address this: virtme: mount /tmp as overlay for O_TMPFILE support https://github.com/multipath-tcp/mptcp-upstream-virtme-docker/pull/43 @Matt This change adds "--overlay-rwdir /tmp" to virtme-run options, ensuring /tmp gets mounted as an overlay filesystem. It functions correctly, though I'm not certain it's the ideal solution. Thanks, -Geliang > crucial that you don't). The upstream CI runs all the selftests in > VMs and they are working just fine.
