Bug in the mmap code?

[ebiederm+eric@ccr.net (Eric W. Biederman)]

I have just been looking through the mmap code, 
with emphases on generic_file_mmap.

What I have discovered is that generic_file_mmap increases file->f_count
but nothing decreases said count.

file->f_count is also increased if a vma is split in half, by an unmap 
operation by the generic code.

Should the generic code handle this or should we leave all of that
work to the open and close methods?

Eric


--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org