WARNING in close_fs_devices

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a87f9628 Linux 4.19.145
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c44873900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6c1d3a90df2d2f09
dashboard link: https://syzkaller.appspot.com/bug?extid=4a14057eb57a04e47261
compiler: gcc (GCC) 10.1.0-syz 20200507

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+4a1405...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 16656 at fs/btrfs/volumes.c:1088 close_fs_devices.part.0.cold+0x11/0x30 fs/btrfs/volumes.c:1088
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 16656 Comm: syz-executor.2 Not tainted 4.19.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
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:close_fs_devices.part.0.cold+0x11/0x30 fs/btrfs/volumes.c:1088
Code: c7 c7 a0 ad be 87 e8 66 8a 79 fe 0f 0b 49 c7 c4 ea ff ff ff e9 03 06 ff ff e8 34 7e 8e fe 48 c7 c7 a0 ad be 87 e8 47 8a 79 fe <0f> 0b e9 e0 0d ff ff e8 1c 7e 8e fe 48 c7 c7 a0 ad be 87 e8 2f 8a
RSP: 0000:ffff8880a4d47b68 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffffffffffffffff RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154d001 RDI: ffffed10149a8f5f
RBP: ffff8880946122c0 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8880a40e0440 R14: ffff88809172db20 R15: ffff88808d93c900
close_fs_devices fs/btrfs/volumes.c:1115 [inline]
btrfs_close_devices+0x95/0x1f0 fs/btrfs/volumes.c:1101
close_ctree+0x3c8/0x850 fs/btrfs/disk-io.c:4047
generic_shutdown_super+0x144/0x370 fs/super.c:456
kill_anon_super+0x36/0x60 fs/super.c:1032
btrfs_kill_super+0x49/0x550 fs/btrfs/super.c:2213
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460027
Code: 64 89 04 25 d0 02 00 00 58 5f ff d0 48 89 c7 e8 2f be ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 fd 89 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffc06d94798 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000460027
RDX: 0000000000403188 RSI: 0000000000000002 RDI: 00007ffc06d94840
RBP: 0000000000002641 R08: 0000000000000000 R09: 000000000000000c
R10: 0000000000000005 R11: 0000000000000246 R12: 00007ffc06d958d0
R13: 0000000002834a60 R14: 0000000000000000 R15: 00007ffc06d958d0
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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 0c88e405 Linux 4.19.160
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=178fc55d500000
kernel config: https://syzkaller.appspot.com/x/.config?x=14b8a4cf9e8340fd

dashboard link: https://syzkaller.appspot.com/bug?extid=4a14057eb57a04e47261
compiler: gcc (GCC) 10.1.0-syz 20200507

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=106930a5500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17dd897d500000

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

BTRFS warning (device <unknown>): duplicate device /dev/loop0 devid 1912602624 generation 7 scanned by syz-executor929 (8704)
BTRFS error (device loop3): bad tree block start, want 5242880 have 0
BTRFS warning (device loop3): failed to read tree root
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8691 at fs/btrfs/volumes.c:1080 close_fs_devices.part.0.cold+0x11/0x30 fs/btrfs/volumes.c:1080

Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8691 Comm: syz-executor929 Not tainted 4.19.160-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
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:close_fs_devices.part.0.cold+0x11/0x30 fs/btrfs/volumes.c:1080
Code: c7 c7 a0 f3 a4 88 e8 aa b2 56 fe 0f 0b 49 c7 c4 ea ff ff ff e9 d7 06 ff ff e8 08 b9 6b fe 48 c7 c7 a0 f3 a4 88 e8 8b b2 56 fe <0f> 0b e9 b4 0e ff ff e8 f0 b8 6b fe 48 c7 c7 a0 f3 a4 88 e8 73 b2
RSP: 0018:ffff8880a2cb7600 EFLAGS: 00010282
RAX: 0000000000000024 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fdb91 RDI: ffffed1014596eb2
RBP: ffff8880b333fd40 R08: 0000000000000024 R09: 0000000000000000

R10: 0000000000000005 R11: 0000000000000000 R12: dffffc0000000000

R13: ffff8880aac93700 R14: ffff888091fb1b60 R15: ffff88809ff2d200
close_fs_devices fs/btrfs/volumes.c:1107 [inline]
btrfs_close_devices+0x95/0x1f0 fs/btrfs/volumes.c:1093
open_ctree+0x26b/0x61e0 fs/btrfs/disk-io.c:3326
btrfs_fill_super fs/btrfs/super.c:1209 [inline]
btrfs_mount_root+0x12e5/0x1830 fs/btrfs/super.c:1613
mount_fs+0xa3/0x30c fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount+0x3c/0x60 fs/namespace.c:951
btrfs_mount+0x23a/0xa93 fs/btrfs/super.c:1681
mount_fs+0xa3/0x30c fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x113c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x44863a
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 cd a2 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 aa a2 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffd8f719b08 EFLAGS: 00000293 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd8f719b80 RCX: 000000000044863a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd8f719b40
RBP: 0000000000000004 R08: 00007ffd8f719b80 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000003
R13: 00007ffd8f719b40 R14: 0000000000000003 R15: 0000000000000001

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 4c97ed4332beba3ed26b2f14461d3cc469c7f27e
Author: Junxiao Bi <junxi...@oracle.com>
Date: Thu Jul 29 21:53:38 2021 +0000

ocfs2: fix zero out valid data

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1265a825300000
start commit: 13d2ce42de8c Linux 4.19.163
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=fac7c3360835a4e0
dashboard link: https://syzkaller.appspot.com/bug?extid=4a14057eb57a04e47261
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108e7923500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11aaa40f500000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: ocfs2: fix zero out valid data

For information about bisection process see: https://goo.gl/tpsmEJ#bisection