summaryrefslogtreecommitdiff
path: root/mm/prio_tree.c
diff options
context:
space:
mode:
authorMinchan Kim <minchan.kim@gmail.com>2011-11-01 04:09:28 +0400
committerLinus Torvalds <torvalds@linux-foundation.org>2011-11-01 04:30:50 +0400
commit21ee9f398be209ccbb62929d35961ca1ed48eec3 (patch)
tree4127e14f4a07a2cb7bc6eb902e9c7b0baab8e84f /mm/prio_tree.c
parent2f1da6421570d064a94e17190a4955c2df99794d (diff)
downloadlinux-21ee9f398be209ccbb62929d35961ca1ed48eec3.tar.xz
vmscan: add barrier to prevent evictable page in unevictable list
When a race between putback_lru_page() and shmem_lock with lock=0 happens, progrom execution order is as follows, but clear_bit in processor #1 could be reordered right before spin_unlock of processor #1. Then, the page would be stranded on the unevictable list. spin_lock SetPageLRU spin_unlock clear_bit(AS_UNEVICTABLE) spin_lock if PageLRU() if !test_bit(AS_UNEVICTABLE) move evictable list smp_mb if !test_bit(AS_UNEVICTABLE) move evictable list spin_unlock But, pagevec_lookup() in scan_mapping_unevictable_pages() has rcu_read_[un]lock() so it could protect reordering before reaching test_bit(AS_UNEVICTABLE) on processor #1 so this problem never happens. But it's a unexpected side effect and we should solve this problem properly. This patch adds a barrier after mapping_clear_unevictable. I didn't meet this problem but just found during review. Signed-off-by: Minchan Kim <minchan.kim@gmail.com> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Cc: Mel Gorman <mel@csn.ul.ie> Cc: Rik van Riel <riel@redhat.com> Cc: Lee Schermerhorn <lee.schermerhorn@hp.com> Acked-by: Johannes Weiner <jweiner@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/prio_tree.c')
0 files changed, 0 insertions, 0 deletions