From: Chengming Zhou <chengming.zhou@linux.dev>
To: Pedro Falcato <pedro.falcato@gmail.com>, mm <linux-mm@kvack.org>
Cc: Linux Regressions <regressions@lists.linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Yosry Ahmed <yosryahmed@google.com>,
Nhat Pham <nphamcs@gmail.com>,
Christian Heusel <christian@heusel.eu>
Subject: Re: zswap_writeback_entry crashes in 6.9.5
Date: Mon, 1 Jul 2024 11:44:25 +0800 [thread overview]
Message-ID: <c56a1b5e-7b8c-4c91-bb89-a821494963ca@linux.dev> (raw)
In-Reply-To: <CAKbZUD1-kqfuV0U+KDKPkQbm=RwzD_A1H3qk_c+bw92CqtMbuw@mail.gmail.com>
On 2024/7/1 01:58, Pedro Falcato wrote:
> Hi everyone,
>
> Reporting a bug I've experienced over the last few releases, all in
> 6.9. I don't have a repro for it (seems to happen randomly?). Distro
> is Arch Linux (which is itself minimally patched, config
> https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/e1057d426590bd2064df83779f8644de519874c0/config).
>
> I understand 6.9.5 is a little old, but as I have no repro I'm posting
> this in case someone has any hints or has hit this before.
>
> dmesg:
> BUG: unable to handle page fault for address: 00000000000315af
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP PTI
> CPU: 5 PID: 90 Comm: kswapd0 Tainted: P U OE
> 6.9.5-arch1-1 #1 b9e5462a84a73f67b5c7c6b73f88d2a6349ae768
> Hardware name: ASUSTeK COMPUTER INC. X542URR/X542URR, BIOS X542URR.310
> 10/29/2021
> RIP: 0010:zswap_writeback_entry+0x128/0x1f0
[...]
> note: kswapd0[90] exited with irqs disabled
I'm wondering why this kswapd has irqs disabled? Seems we don't disable
interrupts in zswap_writeback_entry()?
next prev parent reply other threads:[~2024-07-01 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 17:58 zswap_writeback_entry crashes in 6.9.5 Pedro Falcato
2024-07-01 1:07 ` Nhat Pham
2024-07-19 18:57 ` Pedro Falcato
2024-07-19 20:47 ` Nhat Pham
2024-07-01 3:44 ` Chengming Zhou [this message]
2024-07-02 0:33 ` Builder
2024-07-02 15:28 ` 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=c56a1b5e-7b8c-4c91-bb89-a821494963ca@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=christian@heusel.eu \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=pedro.falcato@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=yosryahmed@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;
as well as URLs for NNTP newsgroup(s).