From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
memxor@gmail.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: Temporarily disable atomic operations in BPF arena
Date: Thu, 14 Mar 2024 19:10:30 +0000 [thread overview]
Message-ID: <171044343097.30186.7484635385194590602.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240314174931.98702-1-puranjay12@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 14 Mar 2024 17:49:31 +0000 you wrote:
> Currently, the x86 JIT handling PROBE_MEM32 tagged accesses is not
> equipped to handle atomic accesses into PTR_TO_ARENA, as no PROBE_MEM32
> tagging is performed and no handling is enabled for them.
>
> This will lead to unsafety as the offset into arena will dereferenced
> directly without turning it into a base + offset access into the arena
> region.
>
> [...]
Here is the summary with links:
- [bpf] bpf: Temporarily disable atomic operations in BPF arena
https://git.kernel.org/bpf/bpf/c/44d79142ede8
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-03-14 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 17:49 [PATCH bpf] bpf: Temporarily disable atomic operations in BPF arena Puranjay Mohan
2024-03-14 19:10 ` 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=171044343097.30186.7484635385194590602.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=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=memxor@gmail.com \
--cc=puranjay12@gmail.com \
--cc=sdf@google.com \
--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