From: Matthew Wilcox (Oracle) Date: Sat, 18 Jun 2022 00:00:17 +0000 (-0400) Subject: filemap: Handle sibling entries in filemap_get_read_batch() X-Git-Tag: v6.1-rc5~1018^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=cb995f4eeba9d268fd4b56c2423ad6c1d1ea1b82;p=platform%2Fkernel%2Flinux-starfive.git filemap: Handle sibling entries in filemap_get_read_batch() If a read races with an invalidation followed by another read, it is possible for a folio to be replaced with a higher-order folio. If that happens, we'll see a sibling entry for the new folio in the next iteration of the loop. This manifests as a NULL pointer dereference while holding the RCU read lock. Handle this by simply returning. The next call will find the new folio and handle it correctly. The other ways of handling this rare race are more complex and it's just not worth it. Reported-by: Dave Chinner Reported-by: Brian Foster Debugged-by: Brian Foster Tested-by: Brian Foster Reviewed-by: Brian Foster Fixes: cbd59c48ae2b ("mm/filemap: use head pages in generic_file_buffered_read") Cc: stable@vger.kernel.org Signed-off-by: Matthew Wilcox (Oracle) --- diff --git a/mm/filemap.c b/mm/filemap.c index 5770688..ffdfbc8 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -2385,6 +2385,8 @@ static void filemap_get_read_batch(struct address_space *mapping, continue; if (xas.xa_index > max || xa_is_value(folio)) break; + if (xa_is_sibling(folio)) + break; if (!folio_try_get_rcu(folio)) goto retry;