From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jchao Sun <sunjunchao2870@gmail.com>, Jan Kara <jack@suse.cz>
Subject: Re: Linux 5.19-rc2
Date: Tue, 14 Jun 2022 10:03:16 -0700 [thread overview]
Message-ID: <20220614170316.GA3690098@roeck-us.net> (raw)
In-Reply-To: <20220613154640.GA3881687@roeck-us.net>
On Mon, Jun 13, 2022 at 08:46:42AM -0700, Guenter Roeck wrote:
>
> There are also various UAF and "spinlock bad magic" BUG/WARNING logs in arm
> boot tests. I don't know if those are new or if I just see them now because
> I enabled KFENCE. Here is an (incomplete) sample.
>
> [ 0.430290] printk: console [ramoops-1] printing thread started
> [ 0.436219] BUG: spinlock bad magic on CPU#0, kdevtmpfs/23
> [ 0.436250] lock: noop_backing_dev_info+0x6c/0x3b0, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> [ 0.436808] CPU: 0 PID: 23 Comm: kdevtmpfs Not tainted 5.19.0-rc2 #1
>
This is caused by commit 10e14073107dd0 ("writeback: Fix inode->i_io_list
not be protected by inode->i_lock error"). Reverting this commit fixes
the problem. Here is a complete backtrace:
BUG: spinlock bad magic on CPU#0, kdevtmpfs/16
lock: noop_backing_dev_info+0x6c/0x3b0, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
CPU: 0 PID: 16 Comm: kdevtmpfs Not tainted 5.19.0-rc2-00001-g8bd0807eb95c #1
Hardware name: ARM RealView Machine (Device Tree Support)
unwind_backtrace from show_stack+0x10/0x14
show_stack from dump_stack_lvl+0x68/0x90
dump_stack_lvl from do_raw_spin_lock+0xa8/0xf4
do_raw_spin_lock from __mark_inode_dirty+0x1a4/0x664
__mark_inode_dirty from simple_setattr+0x44/0x5c
simple_setattr from notify_change+0x404/0x460
notify_change from devtmpfsd+0x1ec/0x2b8
devtmpfsd from kthread+0xe0/0x104
kthread from ret_from_fork+0x14/0x24
Exception stack(0xe0851fb0 to 0xe0851ff8)
1fa0: 00000000 00000000 00000000 00000000
1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
Guenter
next prev parent reply other threads:[~2022-06-14 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 23:36 Linus Torvalds
2022-06-13 7:45 ` Build regressions/improvements in v5.19-rc2 Geert Uytterhoeven
2022-06-13 15:46 ` Linux 5.19-rc2 Guenter Roeck
2022-06-14 17:03 ` Guenter Roeck [this message]
2022-06-14 18:05 ` Jan Kara
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=20220614170316.GA3690098@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sunjunchao2870@gmail.com \
--cc=torvalds@linux-foundation.org \
/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®