From: Dmitry Vyukov <dvyukov@google.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: syzbot <syzbot+909a5177749d7990ffa4@syzkaller.appspotmail.com>,
clm@fb.com, dsterba@suse.com, Josef Bacik <jbacik@fb.com>,
linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: general protection fault in open_fs_devices
Date: Thu, 7 Jun 2018 19:03:23 +0200 [thread overview]
Message-ID: <CACT4Y+Yv4_TjyJtNxso9CLBZPXCUkYZy_1RG_o6ASJdTsLO2Ng@mail.gmail.com> (raw)
In-Reply-To: <0dff7b42-65d2-a29e-2086-938031859004@oracle.com>
On Wed, Jun 6, 2018 at 6:28 PM, Anand Jain <anand.jain@oracle.com> wrote:
>
>
> On 06/06/2018 09:17 PM, syzbot wrote:
>
>
>
> Which means there was some other thread which freed our %fs_devices.
> As this thread is still in open_ctree() so the contending thread can't
> be the ioctl(). So btrfs_free_stale_devices() is the only thread which
> can free our %fs_devices in this case.
>
> This is fixed in [1] in the mailing list.
>
> [1]
> [PATCH 3/3] btrfs: fix race between mkfs and mount
Let's tell about this syzbot:
#syz fix: btrfs: fix race between mkfs and mount
next prev parent reply other threads:[~2018-06-07 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:17 general protection fault in open_fs_devices syzbot
2018-06-06 14:41 ` David Sterba
2018-06-06 16:28 ` Anand Jain
2018-06-07 17:03 ` Dmitry Vyukov [this message]
2018-06-19 18:05 ` David Sterba
2018-06-19 18:27 ` syzbot
2018-07-10 18:43 ` Anand Jain
2018-07-10 18:40 ` syzbot
2018-07-10 18:48 ` Anand Jain
2018-07-10 19:08 ` 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=CACT4Y+Yv4_TjyJtNxso9CLBZPXCUkYZy_1RG_o6ASJdTsLO2Ng@mail.gmail.com \
--to=dvyukov@google.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+909a5177749d7990ffa4@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).