linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* 2.2.14 - pte's not cleared before fop->mmap?
@ 2000-09-21  0:07 Jim Garlick
  0 siblings, 0 replies; only message in thread
From: Jim Garlick @ 2000-09-21  0:07 UTC (permalink / raw)
  To: linux-mm

Hi,

I'm working on a driver (2.2.14 / alpha) which has an mmap facility.  
In my fop->mmap function, just prior to calling remap_page_range to 
actually perform the mapping, I scan the user virtual address space I'm 
about to map to look for pte's that are not clear.  Occasionally I find 
a range that has valid pte's in it, pointing to strange physical addresses:

verify_area_isclean: uaddr=20000800000 already mapped to paddr=0
verify_area_isclean: uaddr=20000802000 already mapped to paddr=1ffff1002000
verify_area_isclean: uaddr=20000804000 already mapped to paddr=0
verify_area_isclean: uaddr=20000806000 already mapped to paddr=1ffff1002000
verify_area_isclean: uaddr=20000808000 already mapped to paddr=0
verify_area_isclean: uaddr=2000080e000 already mapped to paddr=0
verify_area_isclean: uaddr=20000810000 already mapped to paddr=0
verify_area_isclean: uaddr=20000812000 already mapped to paddr=1002000
verify_area_isclean: uaddr=20000814000 already mapped to paddr=1002000
verify_area_isclean: uaddr=20000816000 already mapped to paddr=1002000
verify_area_isclean: uaddr=2000081e000 already mapped to paddr=1ffff0000000
verify_area_isclean: uaddr=20000820000 already mapped to paddr=1002000
verify_area_isclean: uaddr=20000822000 already mapped to paddr=6000
verify_area_isclean: uaddr=20000824000 already mapped to paddr=1ffff0000000
verify_area_isclean: uaddr=20000828000 already mapped to paddr=0
verify_area_isclean: uaddr=2000082a000 already mapped to paddr=6e77c000
verify_area_isclean: uaddr=2000082c000 already mapped to paddr=0
verify_area_isclean: uaddr=2000082e000 already mapped to paddr=0
verify_area_isclean: uaddr=20000830000 already mapped to paddr=1ffff0000000
...


I'm at a loss as to why this is the case.  It looks like do_mmap calls
do_munmap, which calls zap_page_range on the pte's just prior to calling
my fop->mmap function, so the range should be clear, right?

This only occurs occasionally.  Any thoughts would be appreciated.

Jim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2000-09-21  0:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-21  0:07 2.2.14 - pte's not cleared before fop->mmap? Jim Garlick

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox