From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Nhat Pham <nphamcs@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, axelrasmussen@google.com,
baohua@kernel.org, baoquan.he@linux.dev, brauner@kernel.org,
chrisl@kernel.org, david@kernel.org, hannes@cmpxchg.org,
kasong@tencent.com, ljs@kernel.org, mhocko@kernel.org,
qi.zheng@linux.dev, shakeel.butt@linux.dev,
shikemeng@huaweicloud.com, weixugc@google.com,
willy@infradead.org, youngjun.park@lge.com, yuanchu@google.com
Cc: stable@vger.kernel.org, ryncsn@gmail.com
Subject: Re: [PATCH 1/2] mm: vmscan: allow writeout of swapcache folios without anon mappings
Date: Tue, 10 Nov 2026 14:01:29 +0800 [thread overview]
Message-ID: <cb36df5b-ef41-4a2b-b8a9-848d5c12e44c@linux.alibaba.com> (raw)
In-Reply-To: <20261106160432.2552507-2-nphamcs@gmail.com>
On 11/7/26 12:04 AM, Nhat Pham wrote:
> Unfaulted zswap readahead folios can be dirty and in swapcache without
> an anonymous mapping. pageout() rejects them before swap_writeout(),
> so reclaim cannot write them out while their swap entries remain
> referenced.
>
> Allow swapcache folios through the filesystem folio check. They already
> have swap entries and can use the existing swap writeout path. Anonymous
> folios outside swapcache have no mapping and already return PAGE_KEEP.
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Link: https://lore.kernel.org/all/sashiko-outbox-181078@kernel.org/
> Fixes: 84798514db50 ("mm: Remove swap_writepage() and shmem_writepage()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Nhat Pham <nphamcs@gmail.com>
> ---
LGTM.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
next prev parent reply other threads:[~2026-11-10 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:04 [PATCH 0/2] mm: fix swapcache writeout and cluster table publication Nhat Pham
2026-11-06 16:04 ` [PATCH 1/2] mm: vmscan: allow writeout of swapcache folios without anon mappings Nhat Pham
2026-11-10 6:01 ` Baolin Wang [this message]
2026-11-06 16:04 ` [PATCH 2/2] mm/swap: publish cluster tables after reacquiring allocator locks Nhat Pham
2026-11-06 19:59 ` Nhat Pham
2026-11-07 18:02 ` Kairui Song
2026-11-09 16:54 ` Nhat Pham
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=cb36df5b-ef41-4a2b-b8a9-848d5c12e44c@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=brauner@kernel.org \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=nphamcs@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=ryncsn@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=stable@vger.kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=youngjun.park@lge.com \
--cc=yuanchu@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®