* Bug in the mmap code?
@ 1999-01-03 22:00 Eric W. Biederman
1999-01-03 22:36 ` Eric W. Biederman
0 siblings, 1 reply; 2+ messages in thread
From: Eric W. Biederman @ 1999-01-03 22:00 UTC (permalink / raw)
To: linux-mm
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug in the mmap code?
1999-01-03 22:00 Bug in the mmap code? Eric W. Biederman
@ 1999-01-03 22:36 ` Eric W. Biederman
0 siblings, 0 replies; 2+ messages in thread
From: Eric W. Biederman @ 1999-01-03 22:36 UTC (permalink / raw)
To: linux-mm
Dah. We are calling fput everywhere in the generic code just fine.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-01-03 22:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-01-03 22:00 Bug in the mmap code? Eric W. Biederman
1999-01-03 22:36 ` Eric W. Biederman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox