From: syzbot <syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in close_fs_devices (3)
Date: Sun, 29 Nov 2020 05:59:19 -0800 [thread overview]
Message-ID: <000000000000ce88b105b53f4c6d@google.com> (raw)
In-Reply-To: <0000000000007e15b505b530766d@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 6174f052 Add linux-next specific files for 20201127
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=141c9553500000
kernel config: https://syzkaller.appspot.com/x/.config?x=79c69cf2521bef9c
dashboard link: https://syzkaller.appspot.com/bug?extid=a70e2ad0879f160b9217
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11727795500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1793dcc9500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8537 at fs/btrfs/volumes.c:1174 close_fs_devices+0x71d/0x930 fs/btrfs/volumes.c:1174
Modules linked in:
CPU: 1 PID: 8537 Comm: syz-executor956 Not tainted 5.10.0-rc5-next-20201127-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:close_fs_devices+0x71d/0x930 fs/btrfs/volumes.c:1174
Code: e8 88 2f 42 fe 85 db 0f 85 5d f9 ff ff e8 9b 27 42 fe 0f 0b e9 51 f9 ff ff e8 8f 27 42 fe 0f 0b e9 c0 fe ff ff e8 83 27 42 fe <0f> 0b e9 f9 fe ff ff 48 c7 c7 1c 80 ee 8c e8 40 fb 84 fe e9 11 f9
RSP: 0018:ffffc9000183f750 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff88801e07b580 RSI: ffffffff832e99dd RDI: 0000000000000003
RBP: dffffc0000000000 R08: 0000000000000000 R09: ffff88801a17b93b
R10: ffffffff832e98d4 R11: 0000000000000000 R12: ffff88801a17b938
R13: ffff88801a17b9f4 R14: ffff888013e1c908 R15: ffff88801a17b850
FS: 00000000025a7880(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f674003e048 CR3: 0000000012337000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
btrfs_close_devices+0x8e/0x4b0 fs/btrfs/volumes.c:1186
open_ctree+0x3f90/0x4035 fs/btrfs/disk-io.c:3484
btrfs_fill_super fs/btrfs/super.c:1362 [inline]
btrfs_mount_root.cold+0x14/0x165 fs/btrfs/super.c:1731
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1549
fc_mount fs/namespace.c:983 [inline]
vfs_kern_mount.part.0+0xd3/0x170 fs/namespace.c:1013
vfs_kern_mount+0x3c/0x60 fs/namespace.c:1000
btrfs_mount+0x234/0xa20 fs/btrfs/super.c:1791
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1549
do_new_mount fs/namespace.c:2896 [inline]
path_mount+0x12ae/0x1e70 fs/namespace.c:3227
do_mount fs/namespace.c:3240 [inline]
__do_sys_mount fs/namespace.c:3448 [inline]
__se_sys_mount fs/namespace.c:3425 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3425
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4492fa
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:00007ffe66329388 EFLAGS: 00000293 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00000000004492fa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffe663293d0
RBP: 00007ffe66329410 R08: 00007ffe66329410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000003
R13: 00007ffe663293d0 R14: 0000000000000003 R15: 0000000000000005
next prev parent reply other threads:[~2020-11-29 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 20:17 WARNING in close_fs_devices (3) syzbot
2020-11-29 13:59 ` syzbot [this message]
2020-11-29 16:52 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000ce88b105b53f4c6d@google.com \
--to=syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox