[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173559963675.1460841.7357730511716480117.git-patchwork-notify@kernel.org>
Date: Mon, 30 Dec 2024 23:00:36 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel Xu <dxu@...uu.xyz>
Cc: ast@...nel.org, daniel@...earbox.net, eddyz87@...il.com,
andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v2] libbpf: Set MFD_NOEXEC_SEAL when creating memfd
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Mon, 30 Dec 2024 14:31:22 -0700 you wrote:
> Starting from 105ff5339f49 ("mm/memfd: add MFD_NOEXEC_SEAL and
> MFD_EXEC") and until 1717449b4417 ("memfd: drop warning for missing
> exec-related flags"), the kernel would print a warning if neither
> MFD_NOEXEC_SEAL nor MFD_EXEC is set in memfd_create().
>
> If libbpf runs on on a kernel between these two commits (eg. on an
> improperly backported system), it'll trigger this warning.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] libbpf: Set MFD_NOEXEC_SEAL when creating memfd
https://git.kernel.org/bpf/bpf-next/c/1846dd8e3a3e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists