summaryrefslogtreecommitdiffstats
path: root/mm/shmem.c
diff options
context:
space:
mode:
authorVitaly Wool <vitalywool@gmail.com>2017-11-17 15:26:16 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-11-17 16:10:00 -0800
commit5d03a6613957785e94af7a4a6212ad4af66aa5c2 (patch)
tree973176f96aa7dfc154525c1513dc920a2fee912e /mm/shmem.c
parent1334be3657dd02af0591d6d8adf0e6a60a7710a6 (diff)
downloadlinux-5d03a6613957785e94af7a4a6212ad4af66aa5c2.tar.gz
linux-5d03a6613957785e94af7a4a6212ad4af66aa5c2.tar.bz2
linux-5d03a6613957785e94af7a4a6212ad4af66aa5c2.zip
mm/z3fold.c: use kref to prevent page free/compact race
There is a race in the current z3fold implementation between do_compact() called in a work queue context and the page release procedure when page's kref goes to 0. do_compact() may be waiting for page lock, which is released by release_z3fold_page_locked right before putting the page onto the "stale" list, and then the page may be freed as do_compact() modifies its contents. The mechanism currently implemented to handle that (checking the PAGE_STALE flag) is not reliable enough. Instead, we'll use page's kref counter to guarantee that the page is not released if its compaction is scheduled. It then becomes compaction function's responsibility to decrease the counter and quit immediately if the page was actually freed. Link: http://lkml.kernel.org/r/20171117092032.00ea56f42affbed19f4fcc6c@gmail.com Signed-off-by: Vitaly Wool <vitaly.wool@sonymobile.com> Cc: <Oleksiy.Avramchenko@sony.com> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/shmem.c')
0 files changed, 0 insertions, 0 deletions