Hello,
syzbot found the following crash on:
HEAD commit: 1ec8f1f0 Linux 4.14.111
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17cdb9b7200000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fdadf290ea9fc6f9
dashboard link:
https://syzkaller.appspot.com/bug?extid=7d658208ac6421b935b9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+7d6582...@syzkaller.appspotmail.com
R13: 00000000004c76c0 R14: 00000000004dd6e8 R15: 0000000000000004
------------[ cut here ]------------
kernel BUG at fs/btrfs/volumes.c:890!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 24759 Comm: syz-executor.1 Not tainted 4.14.111 #1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff88805b464340 task.stack: ffff88807f478000
RIP: 0010:btrfs_prepare_close_one_device fs/btrfs/volumes.c:890 [inline]
RIP: 0010:__btrfs_close_devices+0x7d8/0xa90 fs/btrfs/volumes.c:915
RSP: 0018:ffff88807f47f700 EFLAGS: 00010246
RAX: 0000000000040000 RBX: ffff8880a5e3db40 RCX: ffffc90008c44000
RDX: 0000000000040000 RSI: ffffffff82655c28 RDI: 0000000000000282
RBP: ffff88807f47f7c8 R08: ffff88805b464340 R09: ffff88805b464c08
kobject: 'loop0' (ffff8880646a2360): kobject_uevent_env
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880a4f37ac0
kobject: 'loop0' (ffff8880646a2360): fill_kobj_path: path
= '/devices/virtual/block/loop0'
R13: ffff8880a5e3dc08 R14: fffffffffffffff4 R15: dffffc0000000000
FS: 00007f2d39cac700(0000) GS:ffff8880aee00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004e6460 CR3: 0000000089999000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
btrfs_close_devices+0x29/0x140 fs/btrfs/volumes.c:948
btrfs_mount+0x1fc5/0x2b14 fs/btrfs/super.c:1642
mount_fs+0x9d/0x2a7 fs/super.c:1237
vfs_kern_mount.part.0+0x5e/0x3d0 fs/namespace.c:1046
vfs_kern_mount+0x40/0x60 fs/namespace.c:1036
kobject: 'loop0' (ffff8880646a2360): kobject_uevent_env
mount_subvol fs/btrfs/super.c:1392 [inline]
btrfs_mount+0x3ce/0x2b14 fs/btrfs/super.c:1563
kobject: 'loop0' (ffff8880646a2360): fill_kobj_path: path
= '/devices/virtual/block/loop0'
mount_fs+0x9d/0x2a7 fs/super.c:1237
vfs_kern_mount.part.0+0x5e/0x3d0 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0x417/0x27d0 fs/namespace.c:2879
kobject: 'loop0' (ffff8880646a2360): kobject_uevent_env
kobject: 'loop0' (ffff8880646a2360): fill_kobj_path: path
= '/devices/virtual/block/loop0'
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xab/0x120 fs/namespace.c:3072
do_syscall_64+0x1eb/0x630 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45b69a
RSP: 002b:00007f2d39caba88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f2d39cabb40 RCX: 000000000045b69a
RDX: 00007f2d39cabae0 RSI: 0000000020000100 RDI: 00007f2d39cabb00
RBP: 0000000000000001 R08: 00007f2d39cabb40 R09: 00007f2d39cabae0
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000005
R13: 00000000004c76c0 R14: 00000000004dd6e8 R15: 0000000000000004
Code: c1 ea 03 0f b6 04 02 84 c0 74 08 3c 03 0f 8e 59 02 00 00 48 8b 45 80
c7 80 10 01 00 00 00 00 00 00 e9 e2 f8 ff ff e8 28 7b f7 fe <0f> 0b e8 21
7b f7 fe 0f 0b 48 89 f7 e8 77 e2 20 ff e9 ad f8 ff
kobject: 'loop0' (ffff8880646a2360): kobject_uevent_env
RIP: btrfs_prepare_close_one_device fs/btrfs/volumes.c:890 [inline] RSP:
ffff88807f47f700
RIP: __btrfs_close_devices+0x7d8/0xa90 fs/btrfs/volumes.c:915 RSP:
ffff88807f47f700
---[ end trace a7b3602c903be63a ]---
kobject: 'loop0' (ffff8880646a2360): fill_kobj_path: path
= '/devices/virtual/block/loop0'
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.