lersek at redhat.com
Sat Jan 10 11:47:03 PST 2015
On 01/10/15 14:37, Will Deacon wrote:
> My hunch is that when a task exits and sets fullmm, end is zero and so the
> old need_flush cases no longer run.
(Disclaimer: I'm completely unfamiliar with this code.)
If you have the following call chain in mind:
then I think that (fullmm != 0) precludes (end == 0).
I grepped the tree for "fullmm", and only tlb_gather_mmu() seems to set
it. There are several instances of that function, but each sets fullmm to:
/* Is it from 0 to ~0? */
tlb->fullmm = !(start | (end+1));
So, a nonzero fullmm seems to imply (end == ~0UL).
(And sure enough, exit_mmap() passes it ((unsigned long)-1) as "end").
> With my original patch, we skipped the
> TLB invalidation (since the task is exiting and we will invalidate the TLB
> for that ASID before the ASID is reallocated) but still did the freeing.
> With the current code, we skip the freeing too, which causes us to leak
> pages on exit.
Yes, the new check prevents
tlb_flush_mmu_free() <--- this
> I guess we can either check need_flush as well as end, or we could set both
> start == end == some_nonzero_value in __tlb_adjust_range when need_flush is
> set. Unfortunately, I'm away from my h/w right now, so it's not easy to test
If you have a patch that applies and builds, I'm glad to test it. I got
a few hours now and I'll have some tomorrow as well. (On Monday I guess
you'll have access to your hardware again.)
More information about the linux-arm-kernel