From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Sasha Levin <sasha.levin-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: bcache: BUG in fuzz testing without devices
Date: Fri, 5 Apr 2013 14:21:10 -0700 [thread overview]
Message-ID: <20130405212110.GD15749@google.com> (raw)
In-Reply-To: <515B056E.6010002-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Tue, Apr 02, 2013 at 12:21:02PM -0400, Sasha Levin wrote:
> Hi all,
>
> It seems that trying to fuzz bcache without any devices triggers a BUG:
>
> That BUG looks very intentional there, any reason for adding it instead of exiting
> if there aren't any devices?
The fuzz tester is meant to stress test some of the btree code - it's a
purely in memory test. But it looks like it's rotted - thanks for the
bug report, I'll disable it for now.
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <koverstreet@google.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: NeilBrown <neilb@suse.de>,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: bcache: BUG in fuzz testing without devices
Date: Fri, 5 Apr 2013 14:21:10 -0700 [thread overview]
Message-ID: <20130405212110.GD15749@google.com> (raw)
In-Reply-To: <515B056E.6010002@oracle.com>
On Tue, Apr 02, 2013 at 12:21:02PM -0400, Sasha Levin wrote:
> Hi all,
>
> It seems that trying to fuzz bcache without any devices triggers a BUG:
>
> That BUG looks very intentional there, any reason for adding it instead of exiting
> if there aren't any devices?
The fuzz tester is meant to stress test some of the btree code - it's a
purely in memory test. But it looks like it's rotted - thanks for the
bug report, I'll disable it for now.
next prev parent reply other threads:[~2013-04-05 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 16:21 bcache: BUG in fuzz testing without devices Sasha Levin
2013-04-02 16:21 ` Sasha Levin
[not found] ` <515B056E.6010002-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-04-05 21:21 ` Kent Overstreet [this message]
2013-04-05 21:21 ` Kent Overstreet
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=20130405212110.GD15749@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neilb-l3A5Bk7waGM@public.gmane.org \
--cc=sasha.levin-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
/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.