Adam Litke 72fad7139b hugetlb: handle write-protection faults in follow_hugetlb_page ...

The follow_hugetlb_page() fix I posted (merged as git commit
5b23dbe817) missed one case.  If the pte is
present, but not writable and write access is requested by the caller to
get_user_pages(), the code will do the wrong thing.  Rather than calling
hugetlb_fault to make the pte writable, it notes the presence of the pte
and continues.

This simple one-liner makes sure we also fault on the pte for this case.
Please apply.

Signed-off-by: Adam Litke <agl@us.ibm.com>
Acked-by: Dave Kleikamp <shaggy@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

2007-12-10 19:43:55 -08:00

..

allocpercpu.c

…

backing-dev.c

…

bootmem.c

…

bounce.c

…

fadvise.c

…

filemap_xip.c

…

filemap.c

…

fremap.c

…

highmem.c

…

hugetlb.c

hugetlb: handle write-protection faults in follow_hugetlb_page

2007-12-10 19:43:55 -08:00

internal.h

…

Kconfig

…

madvise.c

…

Makefile

…

memory_hotplug.c

…

memory.c

…

mempolicy.c

…

mempool.c

…

migrate.c

…

mincore.c

…

mlock.c

…

mmap.c

…

mmzone.c

…

mprotect.c

…

mremap.c

…

msync.c

…

nommu.c

…

oom_kill.c

…

page_alloc.c

…

page_io.c

…

page_isolation.c

…

page-writeback.c

…

pdflush.c

…

prio_tree.c

…

quicklist.c

…

readahead.c

…

rmap.c

…

shmem_acl.c

…

shmem.c

…

slab.c

…

slob.c

Avoid double memclear() in SLOB/SLUB

2007-12-09 10:17:52 -08:00

slub.c

Avoid double memclear() in SLOB/SLUB

2007-12-09 10:17:52 -08:00

sparse-vmemmap.c

…

sparse.c

…

swap_state.c

…

swap.c

…

swapfile.c

…

thrash.c

…

tiny-shmem.c

…

truncate.c

…

util.c

…

vmalloc.c

…

vmscan.c

…

vmstat.c

…