summaryrefslogtreecommitdiffstats
path: root/.gitignore
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2007-10-19 12:19:26 +0200
committerThomas Gleixner <tglx@linutronix.de>2007-10-19 12:19:26 +0200
commit9a24d04a3c26c223f22493492c5c9085b8773d4a (patch)
tree2c541bdeac1f11973ab4fbde5f7c19024c4fecfe /.gitignore
parent4fa4d23fa20de67df919030c1216295664866ad7 (diff)
downloadop-kernel-dev-9a24d04a3c26c223f22493492c5c9085b8773d4a.zip
op-kernel-dev-9a24d04a3c26c223f22493492c5c9085b8773d4a.tar.gz
x86: fix global_flush_tlb() bug
While we were reviewing pageattr_32/64.c for unification, Thomas Gleixner noticed the following serious SMP bug in global_flush_tlb(): down_read(&init_mm.mmap_sem); list_replace_init(&deferred_pages, &l); up_read(&init_mm.mmap_sem); this is SMP-unsafe because list_replace_init() done on two CPUs in parallel can corrupt the list. This bug has been introduced about a year ago in the 64-bit tree: commit ea7322decb974a4a3e804f96a0201e893ff88ce3 Author: Andi Kleen <ak@suse.de> Date: Thu Dec 7 02:14:05 2006 +0100 [PATCH] x86-64: Speed and clean up cache flushing in change_page_attr down_read(&init_mm.mmap_sem); - dpage = xchg(&deferred_pages, NULL); + list_replace_init(&deferred_pages, &l); up_read(&init_mm.mmap_sem); the xchg() based version was SMP-safe, but list_replace_init() is not. So this "cleanup" introduced a nasty bug. why this bug never become prominent is a mystery - it can probably be explained with the (still) relative obscurity of the x86_64 architecture. the safe fix for now is to write-lock init_mm.mmap_sem. Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud