BUG: corrupted list in p9_fd_cancelled (2)
11 views
Skip to first unread message
syzbot
Feb 25, 2021, 10:45:19 AM2/25/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 2d19be46 Linux 4.19.177
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17a0fb82d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a1a8f0ba6627eb7
dashboard link: https://syzkaller.appspot.com/bug?extid=2d1761be4c55a5ab1ca1
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2d1761...@syzkaller.appspotmail.com
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
list_del corruption, ffff88809ea39fb0->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:45!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 24745 Comm: syz-executor.5 Not tainted 4.19.177-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45
libceph: connect [d::]:6789 error -101
Code: e8 3a 47 f7 ff 0f 0b 48 89 ee 48 c7 c7 20 c0 b3 88 e8 29 47 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 bf b3 88 e8 15 47 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 c0 bf b3 88 e8 01 47 f7 ff 0f 0b
RSP: 0018:ffff8880564cf720 EFLAGS: 00010286
libceph: mon0 [d::]:6789 connect error
RAX: 000000000000004e RBX: 0000000000000005 RCX: 0000000000000000
RDX: 000000000000e26e RSI: ffffffff814de301 RDI: ffffed100ac99ed6
RBP: ffff88809ea39fb0 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff88809ea39fb8 R15: ffffffff87c03460
FS: 00007f804b248700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fafd33d2f80 CR3: 0000000059b72000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
ceph: No mds server is up or the cluster is laggy
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del include/linux/list.h:125 [inline]
p9_fd_cancelled+0x71/0x230 net/9p/trans_fd.c:737
p9_client_flush+0x397/0x490 net/9p/client.c:690
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
p9_client_rpc+0x1203/0x1440 net/9p/client.c:797
p9_client_stat+0xfe/0x590 net/9p/client.c:1717
v9fs_refresh_inode+0xb5/0x240 fs/9p/vfs_inode.c:1426
v9fs_lookup_revalidate+0x169/0x210 fs/9p/vfs_dentry.c:102
complete_walk+0x1c6/0x240 fs/namei.c:800
path_lookupat+0x26f/0x8d0 fs/namei.c:2323
filename_lookup+0x1ac/0x5a0 fs/namei.c:2349
user_path_at include/linux/namei.h:57 [inline]
do_fchownat+0xe1/0x1e0 fs/open.c:675
__do_sys_chown fs/open.c:701 [inline]
__se_sys_chown fs/open.c:699 [inline]
__x64_sys_chown+0x77/0xb0 fs/open.c:699
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x465ef9
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f804b248188 EFLAGS: 00000246 ORIG_RAX: 000000000000005c
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465ef9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 00000000004bcd1c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007ffd00b5c43f R14: 00007f804b248300 R15: 0000000000022000
Modules linked in:
---[ end trace 3076ff8f133841ab ]---
RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45
Code: e8 3a 47 f7 ff 0f 0b 48 89 ee 48 c7 c7 20 c0 b3 88 e8 29 47 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 bf b3 88 e8 15 47 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 c0 bf b3 88 e8 01 47 f7 ff 0f 0b
libceph: connect [d::]:6789 error -101
RSP: 0018:ffff8880564cf720 EFLAGS: 00010286
RAX: 000000000000004e RBX: 0000000000000005 RCX: 0000000000000000
RDX: 000000000000e26e RSI: ffffffff814de301 RDI: ffffed100ac99ed6
RBP: ffff88809ea39fb0 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff88809ea39fb8 R15: ffffffff87c03460
FS: 00007f804b248700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fafd33d2f80 CR3: 0000000059b72000 CR4: 00000000001426e0
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 found the following issue on:
HEAD commit: 2d19be46 Linux 4.19.177
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17a0fb82d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a1a8f0ba6627eb7
dashboard link: https://syzkaller.appspot.com/bug?extid=2d1761be4c55a5ab1ca1
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2d1761...@syzkaller.appspotmail.com
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
list_del corruption, ffff88809ea39fb0->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:45!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 24745 Comm: syz-executor.5 Not tainted 4.19.177-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45
libceph: connect [d::]:6789 error -101
Code: e8 3a 47 f7 ff 0f 0b 48 89 ee 48 c7 c7 20 c0 b3 88 e8 29 47 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 bf b3 88 e8 15 47 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 c0 bf b3 88 e8 01 47 f7 ff 0f 0b
RSP: 0018:ffff8880564cf720 EFLAGS: 00010286
libceph: mon0 [d::]:6789 connect error
RAX: 000000000000004e RBX: 0000000000000005 RCX: 0000000000000000
RDX: 000000000000e26e RSI: ffffffff814de301 RDI: ffffed100ac99ed6
RBP: ffff88809ea39fb0 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff88809ea39fb8 R15: ffffffff87c03460
FS: 00007f804b248700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fafd33d2f80 CR3: 0000000059b72000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
ceph: No mds server is up or the cluster is laggy
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del include/linux/list.h:125 [inline]
p9_fd_cancelled+0x71/0x230 net/9p/trans_fd.c:737
p9_client_flush+0x397/0x490 net/9p/client.c:690
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
p9_client_rpc+0x1203/0x1440 net/9p/client.c:797
p9_client_stat+0xfe/0x590 net/9p/client.c:1717
v9fs_refresh_inode+0xb5/0x240 fs/9p/vfs_inode.c:1426
v9fs_lookup_revalidate+0x169/0x210 fs/9p/vfs_dentry.c:102
complete_walk+0x1c6/0x240 fs/namei.c:800
path_lookupat+0x26f/0x8d0 fs/namei.c:2323
filename_lookup+0x1ac/0x5a0 fs/namei.c:2349
user_path_at include/linux/namei.h:57 [inline]
do_fchownat+0xe1/0x1e0 fs/open.c:675
__do_sys_chown fs/open.c:701 [inline]
__se_sys_chown fs/open.c:699 [inline]
__x64_sys_chown+0x77/0xb0 fs/open.c:699
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x465ef9
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f804b248188 EFLAGS: 00000246 ORIG_RAX: 000000000000005c
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465ef9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 00000000004bcd1c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007ffd00b5c43f R14: 00007f804b248300 R15: 0000000000022000
Modules linked in:
---[ end trace 3076ff8f133841ab ]---
RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45
Code: e8 3a 47 f7 ff 0f 0b 48 89 ee 48 c7 c7 20 c0 b3 88 e8 29 47 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 60 bf b3 88 e8 15 47 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 c0 bf b3 88 e8 01 47 f7 ff 0f 0b
libceph: connect [d::]:6789 error -101
RSP: 0018:ffff8880564cf720 EFLAGS: 00010286
RAX: 000000000000004e RBX: 0000000000000005 RCX: 0000000000000000
RDX: 000000000000e26e RSI: ffffffff814de301 RDI: ffffed100ac99ed6
RBP: ffff88809ea39fb0 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff88809ea39fb8 R15: ffffffff87c03460
FS: 00007f804b248700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fafd33d2f80 CR3: 0000000059b72000 CR4: 00000000001426e0
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
Jun 25, 2021, 11:45:13 AM6/25/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages