From: Johannes Weiner <hannes@cmpxchg.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Yosry Ahmed <yosryahmed@google.com>,
Nhat Pham <nphamcs@gmail.com>,
linux-mm@kvack.org, kdevops@lists.linux.dev
Subject: Re: BUG: "spinlock bad magic"
Date: Tue, 5 Mar 2024 13:00:44 -0500 [thread overview]
Message-ID: <20240305180044.GC1491027@cmpxchg.org> (raw)
In-Reply-To: <ZedbIKi-FXx-iEno@manet.1015granger.net>
On Tue, Mar 05, 2024 at 12:49:20PM -0500, Chuck Lever wrote:
> Hi-
>
> I'm testing linux-next and am seeing this BUG pop soon after the
> system boots. Afterwards the system seems otherwise healthy.
>
> BUG: spinlock bad magic on CPU#3, kworker/3:1/41
> lock: zswap+0xd0/0x140, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> CPU: 3 PID: 41 Comm: kworker/3:1 Not tainted 6.8.0-rc7-next-20240304 #1
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014
> Workqueue: cgroup_destroy css_killed_work_fn
> Call Trace:
> <TASK>
> dump_stack_lvl+0x8d/0xb0
> do_raw_spin_lock+0x15e/0x1b0
> ? __pfx_do_raw_spin_lock+0x10/0x10
> ? mark_held_locks+0x5d/0x90
> zswap_memcg_offline_cleanup+0x15/0x50
> mem_cgroup_css_offline+0x14a/0x1b0
> ? css_killed_work_fn+0x21/0x2c0
> css_killed_work_fn+0xb6/0x2c0
> process_one_work+0x4ac/0xb30
> ? __pfx_lock_acquire+0x10/0x10
> ? __pfx_process_one_work+0x10/0x10
> ? __list_add_valid_or_report+0x33/0xc0
> worker_thread+0x392/0x680
> ? __kthread_parkme+0xdc/0x100
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x1ad/0x1f0
> ? kthread+0xf0/0x1f0
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x30/0x50
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1a/0x30
> </TASK>
Thanks Chuck, this should be addressed with a fix that Andrew just
picked up:
https://lore.kernel.org/mm-commits/20240305161123.CA4BCC433C7@smtp.kernel.org/T/#u
next prev parent reply other threads:[~2024-03-05 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 17:49 BUG: "spinlock bad magic" Chuck Lever
2024-03-05 18:00 ` Johannes Weiner [this message]
2024-03-05 18:09 ` Chuck Lever III
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=20240305180044.GC1491027@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--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 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.