From: Matthew Wilcox <willy@infradead.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
Pedro Falcato <pedro.falcato@gmail.com>,
Nhat Pham <nphamcs@gmail.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [regression] oops on heavy compilations ("kernel BUG at mm/zswap.c:1005!" and "Oops: invalid opcode: 0000")
Date: Thu, 29 Aug 2024 23:29:05 +0100 [thread overview]
Message-ID: <ZtD2McWko3uobU-B@casper.infradead.org> (raw)
In-Reply-To: <CAJD7tkZ01PPYMzcTyX_cwr836jGonJT=fwT3ovc4ixW44keRgg@mail.gmail.com>
On Thu, Aug 29, 2024 at 02:54:25PM -0700, Yosry Ahmed wrote:
> Looking at the zswap commits between 6.8 and 6.9, ignoring cleanups
> and seemingly irrelevant patches (e.g. swapoff fixups), I think the
> some likely candidates could be the following, but this is not really
> based on any scientific methodology:
>
> 44c7c734a5132 mm/zswap: split zswap rb-tree
> c2e2ba770200b mm/zswap: only support zswap_exclusive_loads_enabled
> a230c20e63efe mm/zswap: zswap entry doesn't need refcount anymore
> 8409a385a6b41 mm/zswap: improve with alloc_workqueue() call
> 0827a1fb143fa mm/zswap: invalidate zswap entry when swap entry free
>
> I also noticed that you are using z3fold as the zpool. Is the problem
> reproducible with zsmalloc? I wouldn't be surprised if there's a
> z3fold bug somewhere.
You're assuming that it's a zswap/zsmalloc/... bug. If it's a random
scribble, as suggested by Takero Funaki:
https://lore.kernel.org/linux-mm/CAPpoddere2g=kkMzrxuJ1KCG=0Hg1-1v=ppg4dON9wK=pKq2uQ@mail.gmail.com/
then focusing on zswap will not be fruitful.
next prev parent reply other threads:[~2024-08-29 22:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BD22A15A-9216-4FA0-82DF-C7BBF8EE642E@gmail.com>
2024-08-23 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-08-23 12:14 ` Piotr Oniszczuk
2024-08-23 13:13 ` Matthew Wilcox
2024-08-23 14:35 ` Nhat Pham
2024-08-23 14:47 ` Matthew Wilcox
2024-08-23 16:07 ` Yosry Ahmed
2024-08-23 15:06 ` Piotr Oniszczuk
2024-08-23 16:16 ` Nhat Pham
2024-08-23 17:24 ` Piotr Oniszczuk
2024-08-23 18:06 ` Nhat Pham
2024-08-24 10:50 ` Piotr Oniszczuk
2024-08-25 5:55 ` Piotr Oniszczuk
2024-08-25 15:05 ` Pedro Falcato
2024-08-25 16:24 ` Piotr Oniszczuk
2024-08-27 18:48 ` Yosry Ahmed
2024-08-29 15:50 ` Piotr Oniszczuk
2024-08-29 21:54 ` Yosry Ahmed
2024-08-29 22:29 ` Matthew Wilcox [this message]
2024-08-29 22:53 ` Yosry Ahmed
2024-08-31 9:41 ` Piotr Oniszczuk
2024-08-31 17:23 ` Yosry Ahmed
2024-09-02 8:57 ` Piotr Oniszczuk
2024-09-03 17:49 ` Yosry Ahmed
2024-09-03 22:43 ` Nhat Pham
2024-09-04 23:36 ` Yosry Ahmed
2024-09-13 9:03 ` Tomáš Trnka
2024-09-13 17:39 ` Yosry Ahmed
2024-09-03 8:31 ` Aithal, Srikanth
2024-09-03 17:52 ` Yosry Ahmed
2024-09-03 8:49 ` Aithal, Srikanth
2024-08-23 18:42 ` Takero Funaki
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=ZtD2McWko3uobU-B@casper.infradead.org \
--to=willy@infradead.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=pedro.falcato@gmail.com \
--cc=piotr.oniszczuk@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
all inboxes | Powered by JetHome®