Re: [PATCH RFC v2 0/4] bpf, sockmap: Restrict iter-context sockmap updates to sockmap iterators

[Michal Luczaj]

On 11/2/26 02:15, Michal Luczaj wrote:
> Follow-up to Sashiko's report [1] and the decision to restrict which
> iterator may perform sockmap updates [2].
> 
> Short series: remove about-to-be-stale test, restrict updates, add a
> negative test. Related bonus: mark bpf_iter__sockmap::sk as PTR_TRUSTED.
> 
> [1]: https://msgid.link/20260626205814.BAC3C1F000E9@xxxxxxxxxxxxxxx
> [2]: https://msgid.link/87echn2fhd.fsf@xxxxxxxxxxxxxx

Apologies, I forgot to strip the RFC prefix (which I set thinking bpf-next
is closed).

Sashikos reviews just as pointed out by Alexei: bpf_sock_destroy(). I left
out the tracing_iter_filter() change since I was not confident I understood
the reasoning behind it.

thanks,
Michal