Commit 384f1811 authored by Matthew Wilcox's avatar Matthew Wilcox Committed by Greg Kroah-Hartman

dax: Check page->mapping isn't NULL

commit c93db7bb upstream.

If we race with inode destroy, it's possible for page->mapping to be
NULL before we even enter this routine, as well as after having slept
waiting for the dax entry to become unlocked.

Fixes: c2a7d2a1 ("filesystem-dax: Introduce dax_lock_mapping_entry()")
Cc: <stable@vger.kernel.org>
Reported-by: default avatarJan Kara <jack@suse.cz>
Signed-off-by: default avatarMatthew Wilcox <willy@infradead.org>
Reviewed-by: default avatarJohannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: default avatarJan Kara <jack@suse.cz>
Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 111758f7
...@@ -423,7 +423,7 @@ bool dax_lock_mapping_entry(struct page *page) ...@@ -423,7 +423,7 @@ bool dax_lock_mapping_entry(struct page *page)
for (;;) { for (;;) {
mapping = READ_ONCE(page->mapping); mapping = READ_ONCE(page->mapping);
if (!dax_mapping(mapping)) if (!mapping || !dax_mapping(mapping))
break; break;
/* /*
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment