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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4853c74bd7ab Merge tag 'parisc-for-6.5-rc7' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145ed837a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3e75b647285836f2
dashboard link: https://syzkaller.appspot.com/bug?extid=89072f8981ab66c1cc76
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [asma...@codewreck.org da...@davemloft.net edum...@google.com eri...@kernel.org ku...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@crudebyte.com lu...@ionkov.net net...@vger.kernel.org pab...@redhat.com v9...@lists.linux.dev]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef4aada30735/disk-4853c74b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8923163b46b9/vmlinux-4853c74b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32085eff8da1/bzImage-4853c74b.xz

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

list_del corruption. next->prev should be ffff888025992a50, but was ffffc9000498fba0. (next=ffffc9000498fba0)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:62!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5078 Comm: kworker/0:3 Not tainted 6.5.0-rc6-syzkaller-00036-g4853c74bd7ab #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events p9_read_work
RIP: 0010:__list_del_entry_valid+0x133/0x1b0 lib/list_debug.c:62
Code: e8 f2 00 46 fd 0f 0b 48 89 c2 48 c7 c7 60 16 c8 8a e8 e1 00 46 fd 0f 0b 48 89 d1 48 c7 c7 e0 16 c8 8a 48 89 c2 e8 cd 00 46 fd <0f> 0b 48 89 34 24 e8 62 ab b6 fd 48 8b 34 24 e9 e3 fe ff ff 48 89
RSP: 0018:ffffc9000498fb30 EFLAGS: 00010282
RAX: 000000000000006d RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff816a0060 RDI: 0000000000000005
RBP: ffff888025992990 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000001 R12: ffff888015eb57c0
R13: ffff888015eb5810 R14: ffffc9000498fae0 R15: ffff888025992a50
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020404030 CR3: 0000000035514000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:134 [inline]
list_del include/linux/list.h:148 [inline]
p9_conn_cancel+0x6b2/0x910 net/9p/trans_fd.c:215
p9_read_work+0x4d8/0xfb0 net/9p/trans_fd.c:407
process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2600
worker_thread+0x687/0x1110 kernel/workqueue.c:2751
kthread+0x33a/0x430 kernel/kthread.c:389
ret_from_fork+0x2c/0x70 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid+0x133/0x1b0 lib/list_debug.c:62
Code: e8 f2 00 46 fd 0f 0b 48 89 c2 48 c7 c7 60 16 c8 8a e8 e1 00 46 fd 0f 0b 48 89 d1 48 c7 c7 e0 16 c8 8a 48 89 c2 e8 cd 00 46 fd <0f> 0b 48 89 34 24 e8 62 ab b6 fd 48 8b 34 24 e9 e3 fe ff ff 48 89
RSP: 0018:ffffc9000498fb30 EFLAGS: 00010282
RAX: 000000000000006d RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff816a0060 RDI: 0000000000000005
RBP: ffff888025992990 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000001 R12: ffff888015eb57c0
R13: ffff888015eb5810 R14: ffffc9000498fae0 R15: ffff888025992a50
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f064ff665e8 CR3: 0000000042368000 CR4: 0000000000350ef0


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

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