From: "Nathan A. Mourey II" <nmoureyii@ne.rr.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs oops with kernel 3.5-rc4
Date: Wed, 27 Jun 2012 14:57:52 -0400 [thread overview]
Message-ID: <1340823472.2269.31.camel@athena> (raw)
In-Reply-To: <20120626201950.GB24953@localhost.localdomain>
On Tue, 2012-06-26 at 16:19 -0400, Josef Bacik wrote:
> list *(btrfs_finish_ordered_io+0x22)
Reading symbols from /home/nmoureyii/kernel/linux-3.5-rc4/vmlinux...done.
(gdb) list *(btrfs_finish_ordered_io+0x22)
0xc1237552 is in btrfs_finish_ordered_io (fs/btrfs/inode.c:1864).
1859 * fully written.
1860 */
1861 static int btrfs_finish_ordered_io(struct btrfs_ordered_extent *ordered_extent)
1862 {
1863 struct inode *inode = ordered_extent->inode;
1864 struct btrfs_root *root = BTRFS_I(inode)->root;
1865 struct btrfs_trans_handle *trans = NULL;
1866 struct extent_io_tree *io_tree = &BTRFS_I(inode)->io_tree;
1867 struct extent_state *cached_state = NULL;
1868 int compress_type = 0;
(gdb)
And no compression.
next prev parent reply other threads:[~2012-06-27 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 20:09 btrfs oops with kernel 3.5-rc4 Nathan A. Mourey II
2012-06-26 20:19 ` Josef Bacik
2012-06-27 18:57 ` Nathan A. Mourey II [this message]
2012-06-27 21:16 ` Josef Bacik
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=1340823472.2269.31.camel@athena \
--to=nmoureyii@ne.rr.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@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.