From: Jim Garlick <garlick@llnl.gov>
To: linux-mm@kvack.org
Subject: 2.2.14 - pte's not cleared before fop->mmap?
Date: Wed, 20 Sep 2000 17:07:32 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009201700300.6478-100000@spork.llnl.gov> (raw)
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/
reply other threads:[~2000-09-21 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0009201700300.6478-100000@spork.llnl.gov \
--to=garlick@llnl.gov \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox