Re: TLB free bug in 4c640eb4181c ("mm: move pte table reclaim code to memory.c")

>> Original report here:
>>
>> https://github.com/BurntSushi/ripgrep/issues/3494
>>
>> I haven't sent a patch because I *still* don't pretend to have
>> followed what all the tlb_ functions promise to do, and I don't want
>> to submit a subtle patch based just on an LLM telling me what *it*
>> thinks those functions do.  I could trace though all this mess
>> manually, but I bet that one of you actually remembers :)
> 
> The memory.c code is definitely broken. I guess the real question is,
> what the effect of that is.

We should end up in tlb_flush_mmu_tlbonly(tlb) -> tlb_flush(tlb) ->
flush_tlb_mm_range() with the wrong range, so yes, please send a
fix asap, thanks!

-- 
Cheers,

David