The patch titled
Date: Mon, 2 Oct 2023 07:37:24 +0100
has been added to the -mm mm-unstable branch. Its filename is
mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case-fix.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case-fix.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Lorenzo Stoakes <lstoakes@xxxxxxxxx>
Date: Mon, 2 Oct 2023 07:37:24 +0100
Subject: mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case-fix
correct identation as per Christopher's feedback
Link: https://lkml.kernel.org/r/2c7014c0-6343-4e76-8697-3f84f54350bd@lucifer.local
Signed-off-by: Lorenzo Stoakes <lstoakes@xxxxxxxxx>
Reviewed-by: Jan Kara <jack@xxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
Cc: Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/filemap.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/mm/filemap.c~mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case-fix
+++ a/mm/filemap.c
@@ -3314,10 +3314,10 @@ retry_find:
*/
if (unlikely(!folio_test_uptodate(folio))) {
/*
- * If the invalidate lock is not held, the folio was in cache and
- * uptodate and now it is not. Strange but possible since we
- * didn't hold the page lock all the time. Let's drop everything,
- * get the invalidate lock and try again.
+ * If the invalidate lock is not held, the folio was in cache
+ * and uptodate and now it is not. Strange but possible since we
+ * didn't hold the page lock all the time. Let's drop
+ * everything, get the invalidate lock and try again.
*/
if (!mapping_locked) {
folio_unlock(folio);
_
Patches currently in -mm which might be from lstoakes@xxxxxxxxx are
mm-refactor-si_mem_available.patch
mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case.patch
mm-filemap-clarify-filemap_fault-comments-for-not-uptodate-case-fix.patch
