From: Yosry Ahmed <yosry@kernel.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nhat Pham <nphamcs@gmail.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Brian Geffon <bgeffon@google.com>,
Minchan Kim <minchan@kernel.org>,
Richard Chang <richardycc@google.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 07/11] zswap: do not free the entry if its pool is NULL
Date: Tue, 10 Nov 2026 16:37:01 +0000 [thread overview]
Message-ID: <avNIFZ0XVgOUdpDc@google.com> (raw)
In-Reply-To: <20261110054836.1515030-8-senozhatsky@chromium.org>
On Tue, Nov 10, 2026 at 02:48:12PM +0900, Sergey Senozhatsky wrote:
> zswap_entry_free() warns if the entry has no pool (which should never
> happen), skips zs_free() and then frees the entry. A subsequent patch
> embeds zsmalloc handle into zswap_entry, so zsmalloc object will point
> to the entry, and we cannot free the entry while the object is still
> there.
>
> Bail out early and leak the entry, its cgroup charge and stats instead.
>
> Suggested-by: Yosry Ahmed <yosry@kernel.org>
> Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Acked-by: Yosry Ahmed <yosry@kernel.org>
> ---
> mm/zswap.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/mm/zswap.c b/mm/zswap.c
> index 1160bd34e289..dc0400d7e1a3 100644
> --- a/mm/zswap.c
> +++ b/mm/zswap.c
> @@ -787,10 +787,11 @@ static void zswap_entry_free(struct zswap_entry *entry)
> struct zswap_pool *pool = zswap_entry_pool(entry);
>
> zswap_lru_del(entry);
> - if (!WARN_ON_ONCE(!pool)) {
> - zs_free(pool->zs_pool, entry->handle);
> - zswap_pool_put(pool);
> - }
> + if (WARN_ON_ONCE(!pool))
> + return;
> +
> + zs_free(pool->zs_pool, entry->handle);
> + zswap_pool_put(pool);
> if (entry->objcg) {
> obj_cgroup_uncharge_zswap(entry->objcg, entry->length);
> obj_cgroup_put(entry->objcg);
> --
> 2.56.0.506.g506a7eabc5-goog
>
next prev parent reply other threads:[~2026-11-10 16:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 5:48 [PATCH v2 00/11] zsmalloc: redesign object alloc API Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 01/11] zram: drop stale comment in write_incompressible_page() Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 02/11] zram: drop get_slot_handle() and set_slot_handle() Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 03/11] zsmalloc: return handle from obj_allocated() Sergey Senozhatsky
2026-11-10 16:28 ` Yosry Ahmed
2026-11-10 17:37 ` Nhat Pham
2026-11-10 5:48 ` [PATCH v2 04/11] zsmalloc: switch handle type to struct zs_handle Sergey Senozhatsky
2026-11-10 16:35 ` Yosry Ahmed
2026-11-11 4:15 ` Sergey Senozhatsky
2026-11-10 17:40 ` Nhat Pham
2026-11-10 5:48 ` [PATCH v2 05/11] zram: check mem_limit before allocating zsmalloc object Sergey Senozhatsky
2026-11-10 18:37 ` sashiko-bot
2026-11-11 4:20 ` Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 06/11] zram: allocate zsmalloc object under slot lock Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 07/11] zswap: do not free the entry if its pool is NULL Sergey Senozhatsky
2026-11-10 16:37 ` Yosry Ahmed [this message]
2026-11-10 17:42 ` Nhat Pham
2026-11-10 5:48 ` [PATCH v2 08/11] zsmalloc: encode 1-based obj_idx so valid obj is never 0 Sergey Senozhatsky
2026-11-10 16:44 ` Yosry Ahmed
2026-11-11 4:44 ` Sergey Senozhatsky
2026-11-10 17:57 ` Nhat Pham
2026-11-11 4:45 ` Sergey Senozhatsky
2026-11-10 18:37 ` sashiko-bot
2026-11-11 4:24 ` Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 09/11] zsmalloc: embed struct zs_handle into zram and zswap entries Sergey Senozhatsky
2026-11-10 16:57 ` Yosry Ahmed
2026-11-10 17:55 ` Nhat Pham
2026-11-10 5:48 ` [PATCH v2 10/11] zsmalloc: fold zs_obj_write() into zs_store() Sergey Senozhatsky
2026-11-10 17:00 ` Yosry Ahmed
2026-11-10 18:01 ` Nhat Pham
2026-11-11 6:05 ` Sergey Senozhatsky
2026-11-10 5:48 ` [PATCH v2 11/11] zsmalloc: populate new zspage outside class->lock in zs_store() Sergey Senozhatsky
2026-11-10 17:03 ` Yosry Ahmed
2026-11-10 18:06 ` Nhat Pham
2026-11-10 16:16 ` [PATCH v2 00/11] zsmalloc: redesign object alloc API Yosry Ahmed
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=avNIFZ0XVgOUdpDc@google.com \
--to=yosry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=richardycc@google.com \
--cc=senozhatsky@chromium.org \
--cc=yosry.ahmed@linux.dev \
/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.