summaryrefslogtreecommitdiff
path: root/crypto/eseqiv.c
diff options
context:
space:
mode:
authorRusty Russell <rusty@rustcorp.com.au>2009-03-31 03:55:23 (GMT)
committerRusty Russell <rusty@rustcorp.com.au>2009-03-30 11:25:24 (GMT)
commitb7ff99ea53cd16de8f6166c0e98f19a7c6ca67ee (patch)
treefed5a3cf8fc8061967e60b5bbf32e81f3c742822 /crypto/eseqiv.c
parent6afbdd059c27330eccbd85943354f94c2b83a7fe (diff)
downloadlinux-fsl-qoriq-b7ff99ea53cd16de8f6166c0e98f19a7c6ca67ee.tar.xz
lguest: wire up pte_update/pte_update_defer
Impact: intermittent guest segv/crash fix I've been seeing random guest bad address crashes and segmentation faults: bisect led to 4f98a2fee8 (vmscan: split LRU lists into anon & file sets), but that's a red herring. It turns out that lguest never hooked up the pte_update/pte_update_defer calls, so our ptes were not always in sync. After the vmscan commit, the bug became reproducible; now a fsck in a 64MB guest causes reproducible pagetable corruption. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: jeremy@xensource.com Cc: virtualization@lists.osdl.org Cc: stable@kernel.org
Diffstat (limited to 'crypto/eseqiv.c')
0 files changed, 0 insertions, 0 deletions