[v5.15] BUG: corrupted list in p9_fd_cancelled (2)

0 views
Skip to first unread message

syzbot

unread,
Sep 5, 2023, 6:05:06 PM9/5/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8f790700c974 Linux 5.15.130
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=140400d7a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a22cff001b9b10b3
dashboard link: https://syzkaller.appspot.com/bug?extid=6d0d93a1b3e626cac256
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/97d68b3e1757/disk-8f790700.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4ecbd3f0457b/vmlinux-8f790700.xz
kernel image: https://storage.googleapis.com/syzbot-assets/68019fbed619/bzImage-8f790700.xz

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

list_del corruption, ffff8880994fd0b0->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:55!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11303 Comm: syz-executor.4 Not tainted 5.15.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:__list_del_entry_valid+0xe5/0x120 lib/list_debug.c:53
Code: 4c 89 f6 e8 16 18 10 06 0f 0b 48 c7 c7 40 7c d8 8a 4c 89 f6 e8 05 18 10 06 0f 0b 48 c7 c7 a0 7c d8 8a 4c 89 f6 e8 f4 17 10 06 <0f> 0b 48 c7 c7 00 7d d8 8a 4c 89 f6 e8 e3 17 10 06 0f 0b 48 c7 c7
RSP: 0018:ffffc9000483f510 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000100 RCX: a913fa7bd682c400
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff8880994fd000 R08: ffffffff8166588c R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888051908000 R14: ffff8880994fd0b0 R15: dead000000000122
FS: 00007fd8dd1456c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c01f731dd8 CR3: 000000001d81d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:132 [inline]
list_del include/linux/list.h:146 [inline]
p9_fd_cancelled+0x95/0x220 net/9p/trans_fd.c:736
p9_client_flush+0x392/0x570 net/9p/client.c:677
p9_client_rpc+0xb35/0x1290 net/9p/client.c:784
p9_client_create+0x9b4/0x1000 net/9p/client.c:1052
v9fs_session_init+0x1fe/0x1910 fs/9p/v9fs.c:409
v9fs_mount+0x72/0x860 fs/9p/vfs_super.c:126
legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1517
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fd8dec47ae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd8dd1450c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fd8ded672c0 RCX: 00007fd8dec47ae9
RDX: 0000000020000140 RSI: 0000000020000400 RDI: 0000000000000000
RBP: 00007fd8dec9347a R08: 0000000020000480 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fd8ded672c0 R15: 00007ffe7703a128
</TASK>
Modules linked in:
---[ end trace 74df26daade5a601 ]---
RIP: 0010:__list_del_entry_valid+0xe5/0x120 lib/list_debug.c:53
Code: 4c 89 f6 e8 16 18 10 06 0f 0b 48 c7 c7 40 7c d8 8a 4c 89 f6 e8 05 18 10 06 0f 0b 48 c7 c7 a0 7c d8 8a 4c 89 f6 e8 f4 17 10 06 <0f> 0b 48 c7 c7 00 7d d8 8a 4c 89 f6 e8 e3 17 10 06 0f 0b 48 c7 c7
RSP: 0018:ffffc9000483f510 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000100 RCX: a913fa7bd682c400
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff8880994fd000 R08: ffffffff8166588c R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888051908000 R14: ffff8880994fd0b0 R15: dead000000000122
FS: 00007fd8dd1456c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c01f731dd8 CR3: 000000001d81d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Mar 8, 2024, 11:25:17 PMMar 8
to syzkaller...@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