[Android 5.10] BUG: corrupted list in p9_fd_cancelled (3)

3 views
Skip to first unread message

syzbot

unread,
Nov 4, 2023, 2:14:22 PM11/4/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d30b996835c0 Merge branch 'android13-5.10' into branch `an..
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=1043c37f680000
kernel config: https://syzkaller.appspot.com/x/.config?x=f13aac5231b00224
dashboard link: https://syzkaller.appspot.com/bug?extid=8487fe0b929fc4f48bb7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1663eecb680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169aa047680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ba128a3a992/disk-d30b9968.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bbebd4846da7/vmlinux-d30b9968.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3619c8823ed7/bzImage-d30b9968.xz

The issue was bisected to:

commit 1be288fd3b0d2f6c7a763680faa614f4b5a08449
Author: Martin Hundebøll <mar...@geanix.com>
Date: Wed Jun 7 08:27:12 2023 +0000

mmc: meson-gx: remove redundant mmc_request_done() call from irq context

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=123f159aa80000
final oops: https://syzkaller.appspot.com/x/report.txt?x=113f159aa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=163f159aa80000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8487fe...@syzkaller.appspotmail.com
Fixes: 1be288fd3b0d ("mmc: meson-gx: remove redundant mmc_request_done() call from irq context")

list_del corruption, ffff88810ecfde88->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: 1453 Comm: syz-executor235 Not tainted 5.10.199-syzkaller-00307-gd30b996835c0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:__list_del_entry_valid+0xea/0x120 lib/list_debug.c:53
Code: 4c 89 f6 e8 67 90 54 02 0f 0b 48 c7 c7 40 06 60 85 4c 89 f6 e8 56 90 54 02 0f 0b 48 c7 c7 a0 06 60 85 4c 89 f6 e8 45 90 54 02 <0f> 0b 48 c7 c7 00 07 60 85 4c 89 f6 e8 34 90 54 02 0f 0b 48 c7 c7
RSP: 0018:ffffc90001687468 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000100 RCX: 5ce9b53308b50500
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90001687488 R08: ffffffff81521b18 R09: ffffed103ee0a5f8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88810ecfde88 R15: dead000000000122
FS: 00007f2c7b2826c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2c7b339878 CR3: 000000011d225000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:132 [inline]
list_del include/linux/list.h:146 [inline]
p9_fd_cancelled+0x74/0x1d0 net/9p/trans_fd.c:725
p9_client_flush+0x392/0x570 net/9p/client.c:677
p9_client_rpc+0xae6/0x1380 net/9p/client.c:784
p9_client_create+0x9be/0x1130 net/9p/client.c:1052
v9fs_session_init+0x1fa/0x19b0 fs/9p/v9fs.c:406
v9fs_mount+0x75/0x7b0 fs/9p/vfs_super.c:126
legacy_get_tree+0xf1/0x190 fs/fs_context.c:593
vfs_get_tree+0x88/0x290 fs/super.c:1559
do_new_mount+0x28b/0xad0 fs/namespace.c:2899
path_mount+0x56f/0xcb0 fs/namespace.c:3229
do_mount fs/namespace.c:3242 [inline]
__do_sys_mount fs/namespace.c:3450 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3427
__x64_sys_mount+0xbf/0xd0 fs/namespace.c:3427
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7f2c7b2e3719
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 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:00007f2c7b282168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f2c7b36d418 RCX: 00007f2c7b2e3719
RDX: 00000000200001c0 RSI: 0000000020000040 RDI: 0000000000000000
RBP: 00007f2c7b36d410 R08: 0000000020000300 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2c7b36d41c
R13: 000000000000006e R14: 00007fff5afa6f20 R15: 00007fff5afa7008
Modules linked in:
---[ end trace 813a199e10c46369 ]---
RIP: 0010:__list_del_entry_valid+0xea/0x120 lib/list_debug.c:53
Code: 4c 89 f6 e8 67 90 54 02 0f 0b 48 c7 c7 40 06 60 85 4c 89 f6 e8 56 90 54 02 0f 0b 48 c7 c7 a0 06 60 85 4c 89 f6 e8 45 90 54 02 <0f> 0b 48 c7 c7 00 07 60 85 4c 89 f6 e8 34 90 54 02 0f 0b 48 c7 c7
RSP: 0018:ffffc90001687468 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000100 RCX: 5ce9b53308b50500
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90001687488 R08: ffffffff81521b18 R09: ffffed103ee0a5f8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88810ecfde88 R15: dead000000000122
FS: 00007f2c7b2826c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2c7b339878 CR3: 000000011d225000 CR4: 00000000003506b0
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.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection

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

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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