[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176106540703.1157367.9711062469755027347.git-patchwork-notify@kernel.org>
Date: Tue, 21 Oct 2025 16:50:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Shardul Bankar <shardulsb08@...il.com>
Cc: bpf@...r.kernel.org, eddyz87@...il.com, ast@...nel.org,
daniel@...earbox.net, 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,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 bpf] bpf: liveness: clarify get_outer_instance()
handling
in propagate_to_outer_instance()
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Tue, 21 Oct 2025 13:38:46 +0530 you wrote:
> propagate_to_outer_instance() calls get_outer_instance() and uses the
> returned pointer to reset and commit stack write marks. Under normal
> conditions, update_instance() guarantees that an outer instance exists,
> so get_outer_instance() cannot return an ERR_PTR.
>
> However, explicitly checking for IS_ERR(outer_instance) makes this code
> more robust and self-documenting. It reduces cognitive load when reading
> the control flow and silences potential false-positive reports from
> static analysis or automated tooling.
>
> [...]
Here is the summary with links:
- [v3,bpf] bpf: liveness: clarify get_outer_instance() handling in propagate_to_outer_instance()
https://git.kernel.org/bpf/bpf-next/c/96d31dff3fa4
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