From: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
zheng.yan@oracle.com
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:1353
Date: Thu, 8 Jul 2010 17:40:32 +0200 [thread overview]
Message-ID: <201007081740.34000.johannes.hirte@fem.tu-ilmenau.de> (raw)
In-Reply-To: <20100708143109.GR15984@think>
Am Donnerstag 08 Juli 2010, 16:31:09 schrieb Chris Mason:
> Neither Yan nor I have been able to reproduce this locally, but a few
> people have now hit it. Johannes, are you available to try out a
> debugging kernel to try and track this down?
Sure, just tell me what to do. Is it enough to recompile the kernel with debug
options enabled or are special debug patches necessary?
regards,
Johannes
next prev parent reply other threads:[~2010-07-08 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:27 kernel BUG at fs/btrfs/extent-tree.c:1353 Johannes Hirte
2010-07-08 14:31 ` Chris Mason
2010-07-08 15:40 ` Johannes Hirte [this message]
2010-07-14 15:25 ` Johannes Hirte
2010-07-15 0:11 ` Dave Chinner
2010-07-15 18:14 ` Johannes Hirte
2010-07-16 14:59 ` Johannes Hirte
2010-07-19 8:01 ` Miao Xie
2010-07-22 18:07 ` Johannes Hirte
2010-07-23 11:02 ` Daniel J Blueman
2010-07-23 11:14 ` Bob Copeland
2010-07-29 17:09 ` Johannes Hirte
2010-07-29 18:54 ` Jens Axboe
2010-08-13 12:19 ` David Woodhouse
2010-07-11 12:28 ` Johannes Hirte
2010-07-13 12:23 ` Johannes Hirte
2010-07-15 18:30 ` csum errors Johannes Hirte
2010-07-15 19:03 ` Chris Mason
2010-07-15 19:32 ` Johannes Hirte
2010-07-15 19:35 ` Chris Mason
2010-07-15 20:00 ` Johannes Hirte
2010-07-17 4:55 ` Brian Rogers
2010-08-10 21:06 ` Sebastian 'gonX' Jensen
2010-08-14 7:05 ` Brian Rogers
2010-08-14 11:10 ` Sebastian 'gonX' Jensen
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=201007081740.34000.johannes.hirte@fem.tu-ilmenau.de \
--to=johannes.hirte@fem.tu-ilmenau.de \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zheng.yan@oracle.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;
as well as URLs for NNTP newsgroup(s).