From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Vitaly Wool <vitaly.wool@konsulko.se>, Igor Belousov <igor.b@beldev.am>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Nhat Pham <nphamcs@gmail.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH] mm/zblock: use vmalloc for page allocations
Date: Sun, 4 May 2025 15:14:38 +0900 [thread overview]
Message-ID: <q52ddqgi42mgknla4y6i5l65nj57qck6vuuruwcm6lpez7bxmp@3luv4iwjppa6> (raw)
In-Reply-To: <myejh7ow3qwbcptyn2d2nz6td67x2noztu4bxihs5jtqw7s4pk@j2wff5ztuu6a>
On (25/05/04 14:02), Sergey Senozhatsky wrote:
> On (25/05/03 20:46), Vitaly Wool wrote:
> > > Right, and it looks like this:
> > >
> > > [ 762.499278] bug_handler+0x0/0xa8
> > > [ 762.499433] die_kernel_fault+0x1c4/0x36c
> > > [ 762.499616] fault_from_pkey+0x0/0x98
> > > [ 762.499784] do_translation_fault+0x3c/0x94
> > > [ 762.499969] do_mem_abort+0x44/0x94
> > > [ 762.500140] el1_abort+0x40/0x64
> > > [ 762.500306] el1h_64_sync_handler+0xa4/0x120
> > > [ 762.500502] el1h_64_sync+0x6c/0x70
> > > [ 762.500718] __pi_memcpy_generic+0x1e4/0x22c (P)
> > > [ 762.500931] zs_zpool_obj_write+0x10/0x1c
> > > [ 762.501117] zpool_obj_write+0x18/0x24
> > > [ 762.501305] zswap_store+0x490/0x7c4
> > > [ 762.501474] swap_writepage+0x260/0x448
> > > [ 762.501654] pageout+0x148/0x340
> > > [ 762.501816] shrink_folio_list+0xa7c/0xf34
> > > [ 762.502008] shrink_lruvec+0x6fc/0xbd0
> > > [ 762.502189] shrink_node+0x52c/0x960
> > > [ 762.502359] balance_pgdat+0x344/0x738
> > > [ 762.502537] kswapd+0x210/0x37c
> > > [ 762.502691] kthread+0x12c/0x204
> > > [ 762.502920] ret_from_fork+0x10/0x20
> >
> > In fact we don’t know if zsmalloc is actually supposed to work with
> > 16K pages.
>
> Hmm I think it is supposed to work, can't think of a reason why it
> shouldn't.
I'm able to repro, I think. Will try to take a look later today/tonight.
Thank you for the report.
// Feel free to send a patch if you have a fix already.
next prev parent reply other threads:[~2025-05-04 6:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 8:01 Vitaly Wool
2025-05-02 8:07 ` Igor Belousov
2025-05-03 18:46 ` Vitaly Wool
2025-05-04 5:02 ` Sergey Senozhatsky
2025-05-04 6:14 ` Sergey Senozhatsky [this message]
2025-05-05 14:08 ` Johannes Weiner
2025-05-06 2:13 ` Sergey Senozhatsky
2025-05-05 14:29 ` Johannes Weiner
2025-05-06 9:42 ` Uladzislau Rezki
2025-05-06 13:13 ` Yosry Ahmed
2025-05-06 13:27 ` Herbert Xu
2025-05-06 13:37 ` Christoph Hellwig
2025-05-07 5:57 ` Sergey Senozhatsky
2025-05-07 6:08 ` Sergey Senozhatsky
2025-05-07 6:14 ` Sergey Senozhatsky
2025-05-07 6:54 ` Christoph Hellwig
2025-05-08 5:58 ` Sergey Senozhatsky
2025-05-08 6:00 ` Christoph Hellwig
2025-05-08 6:17 ` Sergey Senozhatsky
2025-05-08 6:33 ` Sergey Senozhatsky
2025-05-07 8:50 ` Uladzislau Rezki
2025-05-08 6:07 ` 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=q52ddqgi42mgknla4y6i5l65nj57qck6vuuruwcm6lpez7bxmp@3luv4iwjppa6 \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=igor.b@beldev.am \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=vitaly.wool@konsulko.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox