BUG: corrupted list in p9_conn_cancel (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 513c1a3d3f19 Merge tag 'trace-v6.2-rc6' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12801c2f480000
kernel config: https://syzkaller.appspot.com/x/.config?x=61f14435be465467
dashboard link: https://syzkaller.appspot.com/bug?extid=bd63242d8c12fc9f8f35
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [asma...@codewreck.org da...@davemloft.net edum...@google.com eri...@gmail.com ku...@kernel.org linux-...@vger.kernel.org linu...@crudebyte.com lu...@ionkov.net net...@vger.kernel.org pab...@redhat.com v9fs-de...@lists.sourceforge.net]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/735a73476594/disk-513c1a3d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ce1cf35e40b6/vmlinux-513c1a3d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13e817d2d415/bzImage-513c1a3d.xz

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

list_del corruption, ffff88807c443c70->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:53!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6065 Comm: kworker/1:9 Not tainted 6.2.0-rc7-syzkaller-00013-g513c1a3d3f19 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Workqueue: events p9_read_work
RIP: 0010:__list_del_entry_valid.cold+0x5c/0x72 lib/list_debug.c:53
Code: e8 50 17 f0 ff 0f 0b 48 89 ee 48 c7 c7 a0 9c a6 8a e8 3f 17 f0 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 9d a6 8a e8 2b 17 f0 ff <0f> 0b 4c 89 e9 48 89 ee 48 c7 c7 a0 9e a6 8a e8 17 17 f0 ff 0f 0b
RSP: 0018:ffffc900048a7b58 EFLAGS: 00010282
RAX: 000000000000004e RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888078c9c280 RSI: ffffffff8165314c RDI: fffff52000914f5d
RBP: ffff88807c443c70 R08: 000000000000004e R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000000 R12: dead000000000122
R13: dead000000000100 R14: ffff88807c443c70 R15: 1ffff11010ce1f04
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020404030 CR3: 000000002edc2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:134 [inline]
list_del include/linux/list.h:148 [inline]
p9_conn_cancel+0x6a2/0x920 net/9p/trans_fd.c:215
p9_read_work+0x516/0x1050 net/9p/trans_fd.c:407
process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
worker_thread+0x669/0x1090 kernel/workqueue.c:2436
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid.cold+0x5c/0x72 lib/list_debug.c:53
Code: e8 50 17 f0 ff 0f 0b 48 89 ee 48 c7 c7 a0 9c a6 8a e8 3f 17 f0 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 9d a6 8a e8 2b 17 f0 ff <0f> 0b 4c 89 e9 48 89 ee 48 c7 c7 a0 9e a6 8a e8 17 17 f0 ff 0f 0b
RSP: 0018:ffffc900048a7b58 EFLAGS: 00010282
RAX: 000000000000004e RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888078c9c280 RSI: ffffffff8165314c RDI: fffff52000914f5d
RBP: ffff88807c443c70 R08: 000000000000004e R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000000 R12: dead000000000122
R13: dead000000000100 R14: ffff88807c443c70 R15: 1ffff11010ce1f04
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fca7f28c920 CR3: 0000000079b2d000 CR4: 00000000003506e0
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.