public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Fuad Tabba <tabba@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	puranjay@kernel.org, catalin.marinas@arm.com, will@kernel.org,
	bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, martin.lau@linux.dev,
	eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, xukuohai@huaweicloud.com,
	jakub@cloudflare.com, jpb@kernel.org
Subject: Re: [PATCH v3] arm64: bpf: Force 8-byte alignment for JIT buffer to prevent atomic tearing
Date: Thu, 26 Feb 2026 19:30:19 +0000	[thread overview]
Message-ID: <177213421954.1808439.8748044844634571383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260226075525.233321-1-tabba@google.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 26 Feb 2026 07:55:25 +0000 you wrote:
> struct bpf_plt contains a u64 target field. Currently, the BPF JIT
> allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT
> buffer.
> 
> Because the base address of the JIT buffer can be 4-byte aligned (e.g.,
> ending in 0x4 or 0xc), the relative padding logic in build_plt() fails
> to ensure that target lands on an 8-byte boundary.
> 
> [...]

Here is the summary with links:
  - [v3] arm64: bpf: Force 8-byte alignment for JIT buffer to prevent atomic tearing
    https://git.kernel.org/bpf/bpf/c/ef06fd16d487

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




  parent reply	other threads:[~2026-02-26 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  9:31 [PATCH] arm64: bpf: Fix UBSAN misaligned access in BPF JIT Fuad Tabba
2026-02-25  1:43 ` Xu Kuohai
2026-02-25  9:08   ` Fuad Tabba
2026-02-25  9:46     ` Xu Kuohai
2026-02-25 11:00       ` Fuad Tabba
2026-02-26  1:34         ` Xu Kuohai
2026-02-26  7:55           ` [PATCH v3] arm64: bpf: Force 8-byte alignment for JIT buffer to prevent atomic tearing Fuad Tabba
2026-02-26 18:28             ` Will Deacon
2026-02-26 19:30             ` patchwork-bot+netdevbpf [this message]
2026-02-25 17:47       ` [PATCH] arm64: bpf: Fix UBSAN misaligned access in BPF JIT Will Deacon
2026-02-25 17:53         ` Fuad Tabba
2026-02-25 18:22           ` Will Deacon

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=177213421954.1808439.8748044844634571383.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=catalin.marinas@arm.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jpb@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=puranjay@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    --cc=xukuohai@huaweicloud.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