WARNING in btrfs_orphan_add

6 Aufrufe
Direkt zur ersten ungelesenen Nachricht

syzbot

ungelesen,
29.11.2022, 21:25:4429.11.22
an syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1440e2d5880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=81489ddc2cdbd2dd25e8
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152e346b880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d076e3880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4be9db366a6d/mount_0.gz

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

RDX: 0000000000000d60 RSI: 000000000000c0fe RDI: 0000000020000100
RBP: 00007ffffd622d60 R08: 0000000000000001 R09: 0000000000000034
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007f8d20dfb0e8 R14: 0000000000000000 R15: 0000000000000000
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8113 at fs/btrfs/inode.c:3380 btrfs_orphan_add+0x19e/0x1f0 fs/btrfs/inode.c:3380
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8113 Comm: syz-executor353 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:btrfs_orphan_add+0x19e/0x1f0 fs/btrfs/inode.c:3380
Code: 89 e6 bf fb ff ff ff e8 90 d1 79 fe 41 83 fc fb 0f 84 3e bb 11 05 e8 11 d0 79 fe 44 89 e6 48 c7 c7 40 c3 a4 88 e8 e7 07 0a 05 <0f> 0b e8 fb cf 79 fe 44 89 e1 ba 34 0d 00 00 48 89 ef 48 c7 c6 a0
RSP: 0018:ffff888090507d80 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff88808b07e000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10120a0fa2
RBP: ffff88808b07d150 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 00000000fffffff4
R13: ffff88808b07d1a0 R14: ffff88808b02d4f0 R15: ffff8880b148eac0
btrfs_rmdir+0x1f9/0x610 fs/btrfs/inode.c:4536
vfs_rmdir.part.0+0x10f/0x3d0 fs/namei.c:3882
vfs_rmdir fs/namei.c:3868 [inline]
do_rmdir+0x3fd/0x490 fs/namei.c:3943
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f8d20dbfd79
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 17 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffffd622d58 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007ffffd622d98 RCX: 00007f8d20dbfd79
RDX: 0000000000000d60 RSI: 000000000000c0fe RDI: 0000000020000100
RBP: 00007ffffd622d60 R08: 0000000000000001 R09: 0000000000000034
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007f8d20dfb0e8 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Allen antworten
Antwort an Autor
Weiterleiten
0 neue Nachrichten