From: Chris Mason <clm@fb.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: btrfs extents related oops.
Date: Tue, 5 Aug 2014 09:47:03 -0400 [thread overview]
Message-ID: <53E0E057.1060007@fb.com> (raw)
In-Reply-To: <20140805015758.GA9831@redhat.com>
On 08/04/2014 09:57 PM, Dave Jones wrote:
> On Mon, Aug 04, 2014 at 09:28:45PM -0400, Dave Jones wrote:
> > Possibly related to some changes I've been making to my fuzz tester today
> > to operate on the same file from multiple threads.
> > This was on v3.16-829-g98959948a7ba, but probably exists on earlier trees too
> > given the lack of btrfs specific commits so far this merge window.
>
> reproducer:
>
> trinity -q -l off -c lseek -c write
>
> (Things also go very, very bad if you then try to umount that
> partition - endless oopses, too mangled to parse).
So we're fuzzing lseek and btrfs goes crazy? Looking.
-chris
next prev parent reply other threads:[~2014-08-05 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 1:28 btrfs extents related oops Dave Jones
2014-08-05 1:57 ` Dave Jones
2014-08-05 13:47 ` Chris Mason [this message]
2014-08-05 13:52 ` Chris Mason
2014-08-05 13:56 ` Dave Jones
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=53E0E057.1060007@fb.com \
--to=clm@fb.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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.