From: syzbot <syzbot+15a08eabe3d3838fb641@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, ericvh@kernel.org,
linux-kernel@vger.kernel.org, linux_oss@crudebyte.com,
lucho@ionkov.net, syzkaller-bugs@googlegroups.com,
v9fs@lists.linux.dev
Subject: [syzbot] [v9fs?] BUG: corrupted list in p9_fd_cancelled (3)
Date: Fri, 13 Sep 2024 21:00:27 -0700 [thread overview]
Message-ID: <0000000000004d651706220c61a5@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e936e7d4a83b Merge tag 'spi-fix-v6.11-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=136467c7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=28869f34c32848cf
dashboard link: https://syzkaller.appspot.com/bug?extid=15a08eabe3d3838fb641
compiler: gcc (Debian 12.2.0-14) 12.2.0, 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/d80a1fd7fbf1/disk-e936e7d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7096765887fd/vmlinux-e936e7d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/703093aff5a7/bzImage-e936e7d4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15a08eabe3d3838fb641@syzkaller.appspotmail.com
list_del corruption, ffff88805af61610->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:56!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 10605 Comm: syz.0.1206 Not tainted 6.11.0-rc7-syzkaller-00133-ge936e7d4a83b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:__list_del_entry_valid_or_report+0x108/0x1c0 lib/list_debug.c:56
Code: c7 c7 e0 fe b0 8b e8 97 5e de fc 90 0f 0b 48 c7 c7 40 ff b0 8b e8 88 5e de fc 90 0f 0b 48 c7 c7 a0 ff b0 8b e8 79 5e de fc 90 <0f> 0b 48 89 ca 48 c7 c7 00 00 b1 8b e8 67 5e de fc 90 0f 0b 48 89
RSP: 0018:ffffc9000455f6d0 EFLAGS: 00010282
RAX: 000000000000004e RBX: ffff88805af61550 RCX: ffffc9000f602000
RDX: 0000000000000000 RSI: ffffffff816ceea6 RDI: 0000000000000005
RBP: ffff888025047800 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: ffff88805c934830
R13: 0000000000000005 R14: ffff88805af61610 R15: ffff88805af61618
FS: 00007fedb6f3b6c0(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f375bdfc408 CR3: 000000001eab8000 CR4: 00000000003506f0
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+0xcc8/0x1210 net/9p/client.c:1034
v9fs_session_init+0x1f8/0x1a80 fs/9p/v9fs.c:410
v9fs_mount+0xc6/0xa50 fs/9p/vfs_super.c:122
legacy_get_tree+0x109/0x220 fs/fs_context.c:662
vfs_get_tree+0x8f/0x380 fs/super.c:1800
do_new_mount fs/namespace.c:3472 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3799
do_mount fs/namespace.c:3812 [inline]
__do_sys_mount fs/namespace.c:4020 [inline]
__se_sys_mount fs/namespace.c:3997 [inline]
__x64_sys_mount+0x294/0x320 fs/namespace.c:3997
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fedb617def9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fedb6f3b038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fedb6336130 RCX: 00007fedb617def9
RDX: 0000000020000b80 RSI: 0000000020000040 RDI: 0000000000000000
RBP: 00007fedb61f0b76 R08: 0000000020000180 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fedb6336130 R15: 00007ffd5f34b4f8
</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 e0 fe b0 8b e8 97 5e de fc 90 0f 0b 48 c7 c7 40 ff b0 8b e8 88 5e de fc 90 0f 0b 48 c7 c7 a0 ff b0 8b e8 79 5e de fc 90 <0f> 0b 48 89 ca 48 c7 c7 00 00 b1 8b e8 67 5e de fc 90 0f 0b 48 89
RSP: 0018:ffffc9000455f6d0 EFLAGS: 00010282
RAX: 000000000000004e RBX: ffff88805af61550 RCX: ffffc9000f602000
RDX: 0000000000000000 RSI: ffffffff816ceea6 RDI: 0000000000000005
RBP: ffff888025047800 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: ffff88805c934830
R13: 0000000000000005 R14: ffff88805af61610 R15: ffff88805af61618
FS: 00007fedb6f3b6c0(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f375bdfc408 CR3: 000000001eab8000 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 syzkaller@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 other threads:[~2024-09-14 4:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000004d651706220c61a5@google.com \
--to=syzbot+15a08eabe3d3838fb641@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.