On 2/6/26 21:09, Alexei Starovoitov wrote: > On Fri, Feb 6, 2026 at 1:35 AM Harry Yoo <[email protected]> wrote: >> >> Since kfree() now supports freeing objects allocated with >> kmalloc_nolock(), free one bit in enum object_flags. >> >> Signed-off-by: Harry Yoo <[email protected]> > > For patches 3 and 4: > > Acked-by: Alexei Starovoitov <[email protected]> > > I think patches 3 and 4 are ready. > Would be great to land them for this merge window > (if Vlastimil agrees).
We should have an ack from Catalin for kmemleak. Also better take them out of the RFC and send as 2 non-rfc patches first, with cc list reduced accordingly etc. Then I can put them to -next and try sending second merge window PR next week. Can you also point to any bug reports that would be fixed? (that you had to work around or delay merging or something) that would help the argument to not wait a cycle. > Patch 3 is tiny, but the impact is huge and > patch 4 is a very nice cleanup. > If we land it now we can start using kfree_rcu() on bpf side > in the next release cycle. That will help us a lot.
