Re: [PATCH 6.12 541/602] bpf: Refactor {acquire,release}_reference_state
Harshit Mogalapalli <[email protected]> Mon, 3 Aug 2026 10:39:01 +0530
| Newsgroups | dev.linux.lists.patches,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
Hi Sasha,
On 02/08/26 8:45 am, Sasha Levin wrote:
> On Sat, Aug 01, 2026 at 11:34:53PM +0530, Harshit Mogalapalli wrote:
>> So 769b0f1c8214 is recorded as present although its semantics are
>> absent, while 201b62ccc831 is split across two differently attributed
>> commits.
>
> Confirmed, and thanks for chasing this down - your reading of it is
> correct.
>
>> Maybe we could be replacing 76344b7301ce plus 4ee2d0ce3e82 with one
>> correctly attributed adapted backport of 201b62ccc831 before
>> 6261a33d665b.
>
> For now I've dropped all three from the 6.12 queue:
>
> - bpf: Refactor {acquire,release}_reference_state (769b0f1c8214)
> - bpf: Refactor check_ctx_access() (201b62ccc831)
> - bpf: Reset register bounds before narrowing retval range in
> check_mem_access() (5e0b273e0a62)
>
> I'll requeue the fix next cycle with a corrected dependency set.
>
Thanks again, that plan looks good to me.
regards,
Harshit