[moderation] [v9fs?] BUG: corrupted list in p9_fd_cancelled (3)

0 views
Skip to first unread message

syzbot

unread,
Jun 21, 2024, 10:35:29 PM (8 days ago) Jun 21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2ccbdf43d5e7 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12f434fa980000
kernel config: https://syzkaller.appspot.com/x/.config?x=81c0d76ceef02b39
dashboard link: https://syzkaller.appspot.com/bug?extid=ae38637037fe9021935a
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [asma...@codewreck.org eri...@kernel.org linux-...@vger.kernel.org linu...@crudebyte.com lu...@ionkov.net v9...@lists.linux.dev]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2ccbdf43.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/13cdb5bfbafa/vmlinux-2ccbdf43.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a14f5d07f81/bzImage-2ccbdf43.xz

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

list_del corruption, ffff88802be3c830->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:56!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 3 PID: 6698 Comm: syz-executor.1 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__list_del_entry_valid_or_report+0x108/0x1c0 lib/list_debug.c:56
Code: c7 c7 80 c9 8f 8b e8 47 2f e9 fc 90 0f 0b 48 c7 c7 e0 c9 8f 8b e8 38 2f e9 fc 90 0f 0b 48 c7 c7 40 ca 8f 8b e8 29 2f e9 fc 90 <0f> 0b 48 89 ca 48 c7 c7 a0 ca 8f 8b e8 17 2f e9 fc 90 0f 0b 48 89
RSP: 0018:ffffc90002e676c0 EFLAGS: 00010286
RAX: 000000000000004e RBX: ffff88802be3c770 RCX: ffffffff816f41b9
RDX: 0000000000000000 RSI: ffffffff816fcdb6 RDI: 0000000000000005
RBP: ffff8880258be800 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88804bd9b830
R13: 0000000000000005 R14: ffff88802be3c830 R15: ffff88802be3c838
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:00000000f5ea2b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000c00123e01c CR3: 000000004badc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_del include/linux/list.h:229 [inline]
p9_fd_cancelled+0xa2/0x2a0 net/9p/trans_fd.c:736
p9_client_flush.isra.0+0x34b/0x420 net/9p/client.c:618
p9_client_rpc+0xaef/0xc10 net/9p/client.c:741
p9_client_version net/9p/client.c:930 [inline]
p9_client_create+0xc03/0x11b0 net/9p/client.c:1034
v9fs_session_init+0x1f8/0x1a80 fs/9p/v9fs.c:410
v9fs_mount+0xc6/0xaa0 fs/9p/vfs_super.c:122
legacy_get_tree+0x109/0x220 fs/fs_context.c:662
vfs_get_tree+0x8f/0x380 fs/super.c:1780
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x6e1/0x1f10 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__ia32_sys_mount+0x295/0x320 fs/namespace.c:3875
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf72f2579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f5ea25ac EFLAGS: 00000292 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000020000000
RDX: 0000000020000200 RSI: 0000000000000000 RDI: 0000000020000100
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x108/0x1c0 lib/list_debug.c:56
Code: c7 c7 80 c9 8f 8b e8 47 2f e9 fc 90 0f 0b 48 c7 c7 e0 c9 8f 8b e8 38 2f e9 fc 90 0f 0b 48 c7 c7 40 ca 8f 8b e8 29 2f e9 fc 90 <0f> 0b 48 89 ca 48 c7 c7 a0 ca 8f 8b e8 17 2f e9 fc 90 0f 0b 48 89
RSP: 0018:ffffc90002e676c0 EFLAGS: 00010286
RAX: 000000000000004e RBX: ffff88802be3c770 RCX: ffffffff816f41b9
RDX: 0000000000000000 RSI: ffffffff816fcdb6 RDI: 0000000000000005
RBP: ffff8880258be800 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88804bd9b830
R13: 0000000000000005 R14: ffff88802be3c830 R15: ffff88802be3c838
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:00000000f5ea2b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000c00123e01c CR3: 000000004badc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 10 06 adc %al,(%rsi)
2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi
6: 10 07 adc %al,(%rdi)
8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi
c: 10 08 adc %cl,(%rax)
e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi
1e: 00 51 52 add %dl,0x52(%rcx)
21: 55 push %rbp
22: 89 e5 mov %esp,%ebp
24: 0f 34 sysenter
26: cd 80 int $0x80
* 28: 5d pop %rbp <-- trapping instruction
29: 5a pop %rdx
2a: 59 pop %rcx
2b: c3 ret
2c: 90 nop
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages