syzbot


upstream boot error: BUG: corrupted list in new_inode

Status: auto-obsoleted due to no activity on 2022/12/12 21:30
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+24df94a8d05d5a3e68f0@syzkaller.appspotmail.com
First crash: 620d, last: 620d
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] virtio_net: Revert "virtio_net: set the default max ring size by find_vqs()" 9 (9) 2022/08/15 21:47
[syzbot] upstream boot error: BUG: corrupted list in new_inode 1 (3) 2022/08/15 18:45
Last patch testing requests (3)
Created Duration User Patch Repo Result
2022/08/15 19:19 9m linux@roeck-us.net patch git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.0-rc1 OK
2022/08/15 18:07 7m linux@roeck-us.net https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git fc4d146e8d7d25ef88d409bea1f2e9aff7f30635 error OK
2022/08/15 18:05 9m groeck@google.com https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git fc4d146e8d7d25ef88d409bea1f2e9aff7f30635 OK

Sample crash report:
list_add corruption. next->prev should be prev (ffff8881401c0a00), but was ffff000000000000. (next=ffff88801fb50308).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:27!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 24 Comm: kdevtmpfs Not tainted 5.19.0-syzkaller-14374-g5d6a0f4da927 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:__list_add_valid.cold+0xf/0x58 lib/list_debug.c:27
Code: 48 c7 c6 00 ec 48 8a 48 89 ef 49 c7 c7 ea ff ff ff e8 5b 63 05 00 e9 c2 7d b6 fa 4c 89 e1 48 c7 c7 a0 f2 48 8a e8 95 f2 f0 ff <0f> 0b 48 c7 c7 40 f2 48 8a e8 87 f2 f0 ff 0f 0b 48 c7 c7 a0 f1 48
RSP: 0018:ffffc900001efc10 EFLAGS: 00010286
RAX: 0000000000000075 RBX: ffff8881401c0000 RCX: 0000000000000000
RDX: ffff888012620000 RSI: ffffffff8161f148 RDI: fffff5200003df74
RBP: ffff88801db8b588 R08: 0000000000000075 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000000 R12: ffff88801fb50308
R13: ffff88801fb50308 R14: ffff8881401c0000 R15: ffff88801db8b588
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 __list_add include/linux/list.h:69 [inline]
 list_add include/linux/list.h:88 [inline]
 inode_sb_list_add fs/inode.c:495 [inline]
 new_inode+0x114/0x270 fs/inode.c:1049
 shmem_get_inode+0x19b/0xe00 mm/shmem.c:2306
 shmem_mknod+0x5a/0x1f0 mm/shmem.c:2873
 vfs_mknod+0x4d2/0x7e0 fs/namei.c:3892
 handle_create+0x340/0x4b3 drivers/base/devtmpfs.c:226
 handle drivers/base/devtmpfs.c:391 [inline]
 devtmpfs_work_loop drivers/base/devtmpfs.c:406 [inline]
 devtmpfsd+0x1a4/0x2a3 drivers/base/devtmpfs.c:448
 kthread+0x2e4/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_add_valid.cold+0xf/0x58 lib/list_debug.c:27
Code: 48 c7 c6 00 ec 48 8a 48 89 ef 49 c7 c7 ea ff ff ff e8 5b 63 05 00 e9 c2 7d b6 fa 4c 89 e1 48 c7 c7 a0 f2 48 8a e8 95 f2 f0 ff <0f> 0b 48 c7 c7 40 f2 48 8a e8 87 f2 f0 ff 0f 0b 48 c7 c7 a0 f1 48
RSP: 0018:ffffc900001efc10 EFLAGS: 00010286
RAX: 0000000000000075 RBX: ffff8881401c0000 RCX: 0000000000000000
RDX: ffff888012620000 RSI: ffffffff8161f148 RDI: fffff5200003df74
RBP: ffff88801db8b588 R08: 0000000000000075 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000000 R12: ffff88801fb50308
R13: ffff88801fb50308 R14: ffff8881401c0000 R15: ffff88801db8b588
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 0000000000350ef0

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/08/14 21:30 upstream 5d6a0f4da927 8dfcaa3d .config console log report ci-upstream-kasan-gce-root upstream boot error: BUG: corrupted list in new_inode
* Struck through repros no longer work on HEAD.