From: Josef Bacik <jbacik@fusionio.com>
To: tim <tim@klingt.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: BUG at fs/btrfs/file.c:870
Date: Wed, 14 Aug 2013 15:33:37 -0400 [thread overview]
Message-ID: <20130814193337.GC26269@localhost.localdomain> (raw)
In-Reply-To: <kugg05$88d$1@ger.gmane.org>
On Wed, Aug 14, 2013 at 07:50:05PM +0200, tim wrote:
> hi all,
>
> trying to reproduce [1], i've came across another btrfs bug:
>
You hit the strangest things. I'm going to sit down and write a bunch of unit
tests for this function to verify it is working properly. Thanks,
Josef
next prev parent reply other threads:[~2013-08-14 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 17:50 BUG at fs/btrfs/file.c:870 tim
2013-08-14 19:33 ` Josef Bacik [this message]
2013-08-14 19:42 ` tim
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=20130814193337.GC26269@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tim@klingt.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 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).