Received-SPF: pass (google.com: domain of linux-kernel+bounces-112202-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [RESEND PATCH bpf] bpf: verifier: fix addr_space_cast from as(1) to
 as(0)
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171116462707.20726.11825470378202448490.git-patchwork-notify@kernel.org>
Date: Sat, 23 Mar 2024 03:30:27 +0000
References: <20240321153939.113996-1-puranjay12@gmail.com>
In-Reply-To: <20240321153939.113996-1-puranjay12@gmail.com>
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, bpf@vger.kernel.org,
 linux-kernel@vger.kernel.org

Hello:

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

On Thu, 21 Mar 2024 15:39:39 +0000 you wrote:
> The verifier currently converts addr_space_cast from as(1) to as(0) that
> is: BPF_ALU64 | BPF_MOV | BPF_X with off=1 and imm=1
> to
> BPF_ALU | BPF_MOV | BPF_X with imm=1 (32-bit mov)
> 
> Because of this imm=1, the JITs that have bpf_jit_needs_zext() == true,
> interpret the converted instruction as BPF_ZEXT_REG(DST) which is a
> special form of mov32, used for doing explicit zero extension on dst.
> These JITs will just zero extend the dst reg and will not move the src to
> dst before the zext.
> 
> [...]

Here is the summary with links:
  - [RESEND,bpf] bpf: verifier: fix addr_space_cast from as(1) to as(0)
    https://git.kernel.org/bpf/bpf/c/c49cdf5b88aa

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