From: Sasha Levin <sashal@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Pedro Falcato <pfalcato@suse.de>,
stable@vger.kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>, Song Liu <song@kernel.org>,
Eric Hagberg <ehagberg@janestreet.com>, Zi Yan <ziy@nvidia.com>,
Gregg Leventhal <gleventhal@janestreet.com>,
Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH stable v2] mm/khugepaged: write all dirty file folios when collapsing
Date: Wed, 8 Jul 2026 21:04:47 -0400 [thread overview]
Message-ID: <20260708194323.agent5-0003@kernel.org> (raw)
In-Reply-To: <20260708151357.353173-1-pfalcato@suse.de>
> Fix it by fully writing back the page cache (and waiting) when collapsing
> file THPs. Doing so provides the guarantee that no dirty folio will be
> observed while there are active THPs. To fully ensure this is safe, the
> invalidate_lock needs to be held while doing the writeout, so that
> do_dentry_open()'s page cache truncation excludes this write-and-wait.
Queued for 7.1, 6.18, and 6.12 (with Willy's Reviewed-by and David's
Acked-by from this thread), thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-09 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 15:13 [PATCH stable v2] mm/khugepaged: write all dirty file folios when collapsing Pedro Falcato
2026-07-08 15:30 ` Matthew Wilcox
2026-07-08 16:29 ` Pedro Falcato
2026-07-08 16:28 ` Pedro Falcato
2026-07-10 3:48 ` Baolin Wang
2026-07-08 16:50 ` David Hildenbrand (Arm)
2026-07-09 1:04 ` Sasha Levin [this message]
2026-07-09 9:00 ` Pedro Falcato
2026-07-10 21:03 ` Sasha Levin
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=20260708194323.agent5-0003@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=ehagberg@janestreet.com \
--cc=gleventhal@janestreet.com \
--cc=jack@suse.cz \
--cc=lance.yang@linux.dev \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/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.