From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Bastari Thamrin <thamrinjonathan@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] selftests/bpf: Fix d_path check_mem_access and drop CHECK()
Date: Fri, 13 Nov 2026 21:40:06 +0000 [thread overview]
Message-ID: <179460600678.1853483.7161886083844264787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106-dpath-memfd-v2-0-1dc0799b4aa6@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 06 Nov 2026 10:37:07 +0700 you wrote:
> Patch 1 replaces the deprecated CHECK() calls with ASSERT_*().
>
> Patch 2 fixes check_mem_access, which creates a temp file in
> /dev/shm that isn't mounted under vmtest.sh in local runs. This
> causes mkstemp() to fail with ENOENT. mkstemp() is replaced with
> memfd_create() as it gives a shmem-backed file with no mount
> needed while still reaching vfs_fallocate.
>
> [...]
Here is the summary with links:
- [v2,1/2] selftests/bpf: Replace d_path CHECK() with ASSERT_*()
https://git.kernel.org/bpf/bpf-next/c/ed6624f3e8b6
- [v2,2/2] selftests/bpf: Use memfd_create instead of mkstemp in d_path
https://git.kernel.org/bpf/bpf-next/c/75cf1b5e5489
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-13 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 3:37 Jonathan Bastari Thamrin via B4 Relay
2026-11-06 3:37 ` [PATCH v2 1/2] selftests/bpf: Replace d_path CHECK() with ASSERT_*() Jonathan Bastari Thamrin via B4 Relay
2026-11-06 3:37 ` [PATCH v2 2/2] selftests/bpf: Use memfd_create instead of mkstemp in d_path Jonathan Bastari Thamrin via B4 Relay
2026-11-13 21:40 ` patchwork-bot+netdevbpf [this message]
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=179460600678.1853483.7161886083844264787.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thamrinjonathan@gmail.com \
--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®