From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+5b658d997a83984507a6@syzkaller.appspotmail.com>
Cc: Johannes Thumshirn <jthumshirn@suse.de>,
linux-btrfs@vger.kernel.org,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: kernel BUG at fs/btrfs/volumes.c:LINE!
Date: Sat, 7 Mar 2020 13:53:32 -0800 [thread overview]
Message-ID: <20200307215332.GR15444@sol.localdomain> (raw)
In-Reply-To: <20191205113838.GC11438@Johanness-MacBook-Pro.local>
On Thu, Dec 05, 2019 at 12:38:38PM +0100, Johannes Thumshirn wrote:
> On Thu, Dec 05, 2019 at 11:07:27AM +0100, Dmitry Vyukov wrote:
> > The correct syntax would be (no dash + colon):
> >
> > #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/jth/linux.git
> > close_fs_devices
>
> Ah ok, thanks.
>
> Although syzbot already said it can't test because it has no reproducer.
> Anyways good to know for future reports.
>
> Byte,
> Johannes
Looks like there was a fix for this merged:
commit 321f69f86a0fc40203b43659c3a39464f15c2ee9
Author: Johannes Thumshirn <jthumshirn@suse.de>
Date: Wed Dec 4 14:36:39 2019 +0100
btrfs: reset device back to allocation state when removing
So telling syzbot:
#syz fix: btrfs: reset device back to allocation state when removing
In the future, please use the Reported-by line that syzbot suggested in its
original mail, so that bugs get automatically closed.
prev parent reply other threads:[~2020-03-07 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:31 kernel BUG at fs/btrfs/volumes.c:LINE! syzbot
2018-06-06 16:15 ` Anand Jain
2018-06-07 15:34 ` David Sterba
2018-06-07 16:28 ` Dmitry Vyukov
2018-06-07 16:52 ` David Sterba
2019-06-10 23:14 ` Eric Biggers
2019-06-11 10:01 ` David Sterba
2019-12-04 14:59 ` Johannes Thumshirn
2019-12-05 10:00 ` Johannes Thumshirn
2019-12-05 10:07 ` Dmitry Vyukov
2019-12-05 10:07 ` syzbot
2019-12-05 11:38 ` Johannes Thumshirn
2019-12-05 11:50 ` David Sterba
2019-12-05 12:06 ` Dmitry Vyukov
2019-12-10 15:11 ` Dmitry Vyukov
2020-03-07 21:53 ` Eric Biggers [this message]
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=20200307215332.GR15444@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=syzbot+5b658d997a83984507a6@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