From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: ast@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] libbpf: Set MFD_NOEXEC_SEAL when creating memfd
Date: Mon, 30 Dec 2024 23:00:36 +0000 [thread overview]
Message-ID: <173559963675.1460841.7357730511716480117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6e62c2421ad7eb1da49cbf16da95aaaa7f94d394.1735594195.git.dxu@dxuuu.xyz>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.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
prev parent reply other threads:[~2024-12-30 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 21:31 [PATCH bpf-next v2] libbpf: Set MFD_NOEXEC_SEAL when creating memfd Daniel Xu
2024-12-30 23:00 ` 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=173559963675.1460841.7357730511716480117.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=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--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