diff options
author | Hugh Dickins <hugh@veritas.com> | 2005-10-29 18:16:26 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-10-29 21:40:40 -0700 |
commit | 8f4e2101fd7df9031a754eedb82e2060b51f8c45 (patch) | |
tree | 624db00c6160d70376a57447b45b935b293e396b /fs/proc | |
parent | b462705ac679f6195d1b23a752cda592d9107495 (diff) | |
download | linux-8f4e2101fd7df9031a754eedb82e2060b51f8c45.tar.gz linux-8f4e2101fd7df9031a754eedb82e2060b51f8c45.tar.bz2 linux-8f4e2101fd7df9031a754eedb82e2060b51f8c45.zip |
[PATCH] mm: page fault handler locking
On the page fault path, the patch before last pushed acquiring the
page_table_lock down to the head of handle_pte_fault (though it's also taken
and dropped earlier when a new page table has to be allocated).
Now delete that line, read "entry = *pte" without it, and go off to this or
that page fault handler on the basis of this unlocked peek. Usually the
handler can proceed without the lock, relying on the subsequent locked
pte_same or pte_none test to back out when necessary; though do_wp_page needs
the lock immediately, and do_file_page doesn't check (if there's a race,
install_page just zaps the entry and reinstalls it).
But on those architectures (notably i386 with PAE) whose pte is too big to be
read atomically, if SMP or preemption is enabled, do_swap_page and
do_file_page might cause irretrievable damage if passed a Frankenstein entry
stitched together from unrelated parts. In those configs, "pte_unmap_same"
has to take page_table_lock, validate orig_pte still the same, and drop
page_table_lock before unmapping, before proceeding.
Use pte_offset_map_lock and pte_unmap_unlock throughout the handlers; but lock
avoidance leaves more lone maps and unmaps than elsewhere.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/proc')
0 files changed, 0 insertions, 0 deletions