summaryrefslogtreecommitdiffstats
path: root/mm/filemap.c
diff options
context:
space:
mode:
authorAndi Kleen <ak@linux.intel.com>2012-03-22 00:34:09 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2012-03-22 01:54:58 +0100
commit9a3c531df9462df6cc2b060f749651723ffc180c (patch)
tree448ad57ef6ea3b462849ea1bdd4732e0296e1f4f /mm/filemap.c
parentmm: use global_dirty_limit in throttle_vm_writeout() (diff)
downloadlinux-9a3c531df9462df6cc2b060f749651723ffc180c.tar.xz
linux-9a3c531df9462df6cc2b060f749651723ffc180c.zip
mm: update stale lock ordering comment for memory-failure.c
When i_mmap_lock changed to a mutex the locking order in memory failure was changed to take the sleeping lock first. But the big fat mm lock ordering comment (BFMLO) wasn't updated. Do this here. Pointed out by Andrew. Signed-off-by: Andi Kleen <ak@linux.intel.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to '')
-rw-r--r--mm/filemap.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/mm/filemap.c b/mm/filemap.c
index e8cf8aefd6f6..f3230604006c 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -101,9 +101,8 @@
* ->inode->i_lock (zap_pte_range->set_page_dirty)
* ->private_lock (zap_pte_range->__set_page_dirty_buffers)
*
- * (code doesn't rely on that order, so you could switch it around)
- * ->tasklist_lock (memory_failure, collect_procs_ao)
- * ->i_mmap_mutex
+ * ->i_mmap_mutex
+ * ->tasklist_lock (memory_failure, collect_procs_ao)
*/
/*