From: Chris Mason <chris.mason@oracle.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/disk-io.c:2221!
Date: Mon, 3 Aug 2009 10:02:23 -0400 [thread overview]
Message-ID: <20090803140223.GB3765@think> (raw)
In-Reply-To: <1249120208.14496.3.camel@localhost>
On Sat, Aug 01, 2009 at 11:50:08AM +0200, Thomas Meyer wrote:
> kernel BUG at fs/btrfs/disk-io.c:2221!
> invalid opcode: 0000 [#1] PREEMPT SMP
> last sysfs file: /sys/block/sdc/sdc1/start
Could you please confirm that line 2221 in your disk-io.c looks like
this:
2219 int btrfs_free_fs_root(struct btrfs_fs_info *fs_info, struct
btrfs_root *root)
2220 {
2221 WARN_ON(!RB_EMPTY_ROOT(&root->inode_tree));
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2222 radix_tree_delete(&fs_info->fs_roots_radix,
2223 (unsigned long)root->root_key.objectid);
2224 if (root->anon_super.s_dev) {
2225 down_write(&root->anon_super.s_umount);
2226 kill_anon_super(&root->anon_super);
2227 }
That's in the unmount path but not under write_ctree_supers, so I want
to make sure I'm looking at the right bug ;)
-chris
prev parent reply other threads:[~2009-08-03 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 9:50 kernel BUG at fs/btrfs/disk-io.c:2221! Thomas Meyer
2009-08-01 18:34 ` Diego Calleja
2009-08-03 14:02 ` Chris Mason [this message]
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=20090803140223.GB3765@think \
--to=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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