Re: [PATCH 6.12.y v4 0/3] bpf: fix dynptr release handling

[Greg KH <gregkh@linuxfoundation.org>]

On Mon, Aug 31, 2026 at 08:15:49AM +0800, Xu Yunxiang wrote:
> Upstream commit 308c7a0ae885 ("bpf: Refactor object relationship
> tracking and fix dynptr UAF bug") fixes these lifetime bugs as part of
> an 11-file parent_id refactor. That refactor cannot be applied to
> 6.12.y, which still represents the relationships with dynptr_id and
> ref_obj_id.
> 
> This series supplies three stable-sized equivalents using the existing
> 6.12.y representation. Patch 1 invalidates slice registers with the
> released dynptr_id. Patch 2 propagates a referenced-dynptr release
> error instead of turning a callback rejection into a kernel warning.
> Patch 3 scans every active call frame when invalidating cloned dynptr
> stack slots. They are split because the bugs have different
> introducing commits and independently testable effects.
> 
> These patches are stable-specific implementations authored for the old
> verifier, not cherry-picks of Amery Hung's upstream diff. Each commit
> keeps 308c7a0ae885 as the upstream provenance for the equivalent fix
> and documents how its implementation differs.
> 
> Changes in v4:
> 
> - make Xu Yunxiang the author of all three stable-specific
>   implementations;
> - remove the authorship, sign-off, and ack trailers copied from
>   308c7a0ae885 because those developers did not write or review these
>   rewritten stable patches;

That's not ok at all!  Take the original commit, and "just" backport
that, keeping the original changelog and authorship information
everywhere.

To pass this off as your own work isn't ok.

Also, you forgot the 6.18 and 7.1 trees, we can't take fixes only for
older kernels.

Please fix up all of these and do it properly.

thanks,

greg k-h