Re: [PATCH 0/4] plugging some mmap() leaks

Ramsay Jones [off-list ref] writes:

If you look at the (currently 31) calls to munmap(), only one seems to look
at the return (in refs/packed-backend.c:183). So, calling munmap() twice
on the same memory region will probably go unnoticed when NO_MMAP is not
set. I have no idea why munmap() was called twice on the same memory region,
since I didn't track down the code responsible.

It was just an FYI about a _potential_ lurking bug when using the mmap compat
routines.

Have I cleared that up, or confused you more. :)

Oh, absolutely.  Thanks.