From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Michael Fara <admin@windowsforum.com>
Cc: senozhatsky@chromium.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mjfara@gmail.com, Minchan Kim <minchan@kernel.org>,
Brian Geffon <bgeffon@google.com>
Subject: Re: [PATCH] mm/zsmalloc: fix NULL pointer dereference in get_next_zpdesc
Date: Wed, 18 Feb 2026 14:01:22 +0900 [thread overview]
Message-ID: <xdxeirrwcmxxue2wha5vkqfle5q56mkuifv6ovunrimbz2b3ws@yq2ww4e3ub63> (raw)
In-Reply-To: <20260209193708.69454-1-mjfara@gmail.com>
Cc-ing Minchan and Brian.
On (26/02/09 19:37), Michael Fara wrote:
> get_next_zpdesc() calls get_zspage() which unconditionally dereferences
> zpdesc->zspage without a NULL check. This causes a kernel oops when
> zpdesc->zspage has been set to NULL by reset_zpdesc() during a race
> between zspage destruction and page compaction/migration.
>
> The race window is documented in a TODO comment in zs_page_migrate():
>
> "nothing prevents a zspage from getting destroyed while it is
> isolated for migration, as the page lock is temporarily dropped
> after zs_page_isolate() succeeded"
>
> The sequence is:
> 1. Compaction calls zs_page_isolate() on a zpdesc, then drops its
> page lock.
> 2. Concurrently, async_free_zspage() or free_zspage() destroys the
> zspage, calling reset_zpdesc() which sets zpdesc->zspage = NULL.
> 3. A subsequent zs_free() path calls trylock_zspage(), which iterates
> zpdescs via get_next_zpdesc(). get_zspage() dereferences the now-
> NULL backpointer, causing:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> RIP: 0010:free_zspage+0x26/0x100
> Call Trace:
> zs_free+0xf4/0x110
> zswap_entry_free+0x7e/0x160
>
> The migration side already has a NULL guard (zs_page_migrate line 1675:
> "if (!zpdesc->zspage) return 0;"), but get_next_zpdesc() lacks the same
> protection.
>
> Fix this by reading zpdesc->zspage directly in get_next_zpdesc()
> instead of going through get_zspage(), and returning NULL when the
> backpointer is NULL. This stops iteration safely — the caller treats
> it as the end of the page chain.
>
> Signed-off-by: Michael Fara <mjfara@gmail.com>
JFI: all of your emails ended up in the SPAM folder, somehow.
Recovered.
[..]
> @@ -735,7 +735,19 @@ static struct zspage *get_zspage(struct zpdesc *zpdesc)
>
> static struct zpdesc *get_next_zpdesc(struct zpdesc *zpdesc)
> {
> - struct zspage *zspage = get_zspage(zpdesc);
> + struct zspage *zspage = zpdesc->zspage;
> +
> + /*
> + * If the backpointer is NULL, this zpdesc was already freed via
> + * reset_zpdesc() by a racing async_free_zspage() while isolated
> + * for compaction. See the TODO comment in zs_page_migrate().
> + */
> + if (unlikely(!zspage)) {
> + WARN_ON_ONCE(1);
What is the purpose of this WARN_ON_ONCE()?
> + return NULL;
> + }
> +
> + BUG_ON(zspage->magic != ZSPAGE_MAGIC);
We can't add new BUG_ON().
> if (unlikely(ZsHugePage(zspage)))
> return NULL;
> --
> 2.39.0
next prev parent reply other threads:[~2026-02-18 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 19:37 Michael Fara
2026-02-18 5:01 ` Sergey Senozhatsky [this message]
2026-02-18 5:46 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2026-02-09 19:36 Michael Fara
2026-02-09 19:32 Michael Fara
2026-02-09 22:50 ` Joshua Hahn
2026-02-09 23:16 ` Joshua Hahn
2026-02-18 5:56 ` Sergey Senozhatsky
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=xdxeirrwcmxxue2wha5vkqfle5q56mkuifv6ovunrimbz2b3ws@yq2ww4e3ub63 \
--to=senozhatsky@chromium.org \
--cc=admin@windowsforum.com \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=mjfara@gmail.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