From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Johannes Thumshirn <jth@kernel.org>,
syzbot <syzbot+5b658d997a83984507a6@syzkaller.appspotmail.com>,
Chris Mason <clm@fb.com>,
dsterba@suse.com, linux-btrfs@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: kernel BUG at fs/btrfs/volumes.c:LINE!
Date: Thu, 5 Dec 2019 12:50:33 +0100 [thread overview]
Message-ID: <20191205115033.GJ2734@suse.cz> (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.
According to
https://syzkaller.appspot.com/bug?id=d50670eeb21302915bde3f25871dfb7ea43db1e4
there is a way how to test it, many reports and the last one about a
week old. Is there a way to instruct syzbot to run the same tests on a
given branch?
(The reproducer is basically setting up environment with limited amount
of memory available for allocation and this hits the BUG_ON.)
next prev parent reply other threads:[~2019-12-05 11:50 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 [this message]
2019-12-05 12:06 ` Dmitry Vyukov
2019-12-10 15:11 ` Dmitry Vyukov
2020-03-07 21:53 ` Eric Biggers
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=20191205115033.GJ2734@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dvyukov@google.com \
--cc=jth@kernel.org \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.