BUG: corrupted list in __percpu_counter_init

4 views
Skip to first unread message

syzbot

unread,
Nov 20, 2022, 2:17:42 PM11/20/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9500fc6e9e60 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=10bf80d9880000
kernel config: https://syzkaller.appspot.com/x/.config?x=b25c9f218686dd5e
dashboard link: https://syzkaller.appspot.com/bug?extid=da394d6b03f414523e27
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1363e60652f7/disk-9500fc6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fcc4da811bb6/vmlinux-9500fc6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b554298f1fa/Image-9500fc6e.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+da394d...@syzkaller.appspotmail.com

list_add corruption. next->prev should be prev (ffff80000d692f08), but was 509cbac6cd31b835. (next=ffff000114ea3268).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:29!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 27121 Comm: syz-executor.0 Not tainted 6.1.0-rc5-syzkaller-32269-g9500fc6e9e60 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __list_add_valid+0x9c/0xb8 lib/list_debug.c:27
lr : __list_add_valid+0x9c/0xb8 lib/list_debug.c:27
sp : ffff800014fc3a10
x29: ffff800014fc3a10 x28: ffff0000c02c8000 x27: 0000000000000000
x26: 0000000000008000 x25: 0000000000000000 x24: 0000000000000000
x23: ffff000114ea3268 x22: ffff80000d692f08 x21: 0000000000000000
x20: ffff000126bce300 x19: ffff000126bce2b8 x18: 00000000000000c0
x17: 3830663239366430 x16: ffff80000dc18158 x15: ffff0000c02c8000
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c02c8000
x11: ff808000081c6510 x10: 0000000000000000 x9 : dd545169f3e68f00
x8 : dd545169f3e68f00 x7 : ffff80000c0b2b74 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0001fefddcc8 x1 : 0000000100000001 x0 : 0000000000000075
Call trace:
__list_add_valid+0x9c/0xb8 lib/list_debug.c:27
__list_add include/linux/list.h:69 [inline]
list_add include/linux/list.h:88 [inline]
__percpu_counter_init+0xe0/0x134 lib/percpu_counter.c:158
fprop_local_init_percpu+0x34/0x88 lib/flex_proportions.c:172
wb_init+0x1e0/0x328 mm/backing-dev.c:310
cgwb_bdi_init mm/backing-dev.c:614 [inline]
bdi_init+0xcc/0x118 mm/backing-dev.c:789
bdi_alloc+0x40/0xbc mm/backing-dev.c:800
super_setup_bdi_name+0x4c/0x120 fs/super.c:1585
super_setup_bdi+0x50/0x8c fs/super.c:1612
v9fs_fill_super fs/9p/vfs_super.c:76 [inline]
v9fs_mount+0x1a4/0x568 fs/9p/vfs_super.c:137
legacy_get_tree+0x30/0x74 fs/fs_context.c:610
vfs_get_tree+0x40/0x140 fs/super.c:1531
do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
path_mount+0x358/0x890 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x2c4/0x3c4 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
Code: f001b780 91266c00 aa0803e1 94aa87a5 (d4210000)
---[ end trace 0000000000000000 ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Feb 14, 2023, 2:13:40 PM2/14/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages