From: "David Hildenbrand (Arm)" <david@kernel.org>
To: sashiko-reviews@lists.linux.dev,
Kiryl Shutsemau <kirill@shutemov.name>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Kiryl Shutsemau (Meta)" <kas@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Hugh Dickins <hughd@google.com>, Chris Mason <mason@kernel.org>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, kernel-team@meta.com
Subject: Re: [PATCH] mm/memory: refuse to map page cache folios that are not uptodate
Date: Sat, 7 Nov 2026 19:17:52 +0100 [thread overview]
Message-ID: <8cd50b75-0845-4e82-a8ed-acfd3a261a3e@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-202966@kernel.org>
On 11/7/26 15:43, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential
> issues to consider:
> - [Medium] mm: user-triggerable WARN_ONCE in do_set_pmd() via
> MADV_COLLAPSE on fallocated shmem THP
... which we are fixing already.
> - [Medium] mm: missing folio_test_uptodate() recheck in
> do_shared_fault() mkwrite path
Kiryl, can you look into that?
> It also noticed 1 related pre-existing issue this patch does not
> introduce:
> - [High] mm/khugepaged: leak of vmf.prealloc_pte in set_huge_pmd() on
> fallback [1]
... which we are fixing already.
--
Cheers,
David
next prev parent reply other threads:[~2026-11-07 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 14:43 [PATCH] mm/memory: refuse to map page cache folios that are not uptodate Kiryl Shutsemau
2026-11-07 14:43 ` sashiko-bot
2026-11-07 18:17 ` David Hildenbrand (Arm) [this message]
2026-11-09 11:32 ` Kiryl Shutsemau
2026-11-09 11:37 ` Pedro Falcato
2026-11-09 11:50 ` David Hildenbrand (Arm)
2026-11-09 11:58 ` Kiryl Shutsemau
2026-11-09 12:18 ` Pedro Falcato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cd50b75-0845-4e82-a8ed-acfd3a261a3e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=kirill@shutemov.name \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mason@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.