From: Wenwu Hou <hwenwur@gmail.com>
To: hannes@cmpxchg.org, yosry@kernel.org, nphamcs@gmail.com
Cc: chengming.zhou@linux.dev, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wenwu Hou <hwenwur@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH] mm: zswap: set zswap_ever_enabled when enabling zswap at runtime
Date: Tue, 20 Oct 2026 20:29:42 +0800 [thread overview]
Message-ID: <20261020122942.3477541-1-hwenwur@gmail.com> (raw)
zswap can end up enabled without zswap_ever_enabled being set, which
leads to data corruption. With CONFIG_ZSWAP_DEFAULT_ON=n:
1. zswap_setup() fails to create the initial pool. Setup still counts
as successful, but zswap_has_pool stays false.
2. The user writes a compressor name to
/sys/module/zswap/parameters/compressor.
zswap_compressor_param_set() creates a pool and sets
zswap_has_pool = true, but never enables the zswap_ever_enabled
static key.
3. The user runs "echo Y > /sys/module/zswap/parameters/enabled".
4. zswap_store() now stores pages in zswap, and swap_writeout() skips
writing them to the swap device.
5. On swap-in, zswap_load() first checks zswap_never_enabled(). It
returns true, so zswap_load() reports that the page is not in zswap.
The page is then read from the swap device, which holds stale data.
Fix this by enabling zswap_ever_enabled in zswap_enabled_param_set()
before zswap_enabled becomes true.
Fixes: 2d4d2b1cfb85 ("mm: zswap: add zswap_never_enabled()")
Cc: stable@vger.kernel.org
Signed-off-by: Wenwu Hou <hwenwur@gmail.com>
---
mm/zswap.c | 25 +++++++++++++++++++++----
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a/mm/zswap.c b/mm/zswap.c
index 37f34e406c8e3..d2b4c248baa67 100644
--- a/mm/zswap.c
+++ b/mm/zswap.c
@@ -629,12 +629,29 @@ static int zswap_enabled_param_set(const char *val,
if (zswap_setup())
break;
fallthrough;
- case ZSWAP_INIT_SUCCEED:
- if (!zswap_has_pool)
+ case ZSWAP_INIT_SUCCEED: {
+ bool enable;
+
+ if (!zswap_has_pool) {
pr_err("can't enable, no pool configured\n");
- else
- ret = param_set_bool(val, kp);
+ break;
+ }
+
+ /*
+ * The initial pool may have been created later by the
+ * compressor param rather than by zswap_setup(), in which
+ * case zswap_ever_enabled is still off. Flip it before
+ * zswap_enabled becomes visible to zswap_store(), otherwise
+ * zswap_load() would skip stored entries and read stale data
+ * from the backing swap device. param_set_bool() treats a
+ * NULL value as true.
+ */
+ if (!val || (!kstrtobool(val, &enable) && enable))
+ static_branch_enable(&zswap_ever_enabled);
+
+ ret = param_set_bool(val, kp);
break;
+ }
case ZSWAP_INIT_FAILED:
pr_err("can't enable, initialization failed\n");
}
--
2.43.0
reply other threads:[~2026-10-20 12:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261020122942.3477541-1-hwenwur@gmail.com \
--to=hwenwur@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yosry@kernel.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 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®