From: Chris Mason <chris.mason@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: lists@nerdbynature.de, linux-btrfs@vger.kernel.org
Subject: Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60
Date: Mon, 8 Feb 2010 16:46:19 -0500 [thread overview]
Message-ID: <20100208214619.GB2814@think> (raw)
In-Reply-To: <20100205.224310.06173989.davem@davemloft.net>
On Fri, Feb 05, 2010 at 10:43:10PM -0800, David Miller wrote:
> From: Christian Kujau <lists@nerdbynature.de>
> Date: Fri, 5 Feb 2010 22:28:47 -0800 (PST)
>
> > Hm, now it looks like this, but I don't know how it'd reveal more
> > information:
> >
> > [ 210.707051] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> > [ 210.802236] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> > [ 210.874620] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> > [ 210.969899] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> > [ 228.724982] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> > [ 228.820220] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> > [ 228.892286] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> > [ 228.987851] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> >
> > I'm open for more patches :-)
>
> Confusing for me too. I'll try to think about this some more.
It is probably the directory code. I switched that to crc32c since
you tried things.
-chris
prev parent reply other threads:[~2010-02-08 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 18:36 Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 Christian Kujau
2010-02-05 20:01 ` David Miller
2010-02-06 5:13 ` Christian Kujau
2010-02-06 5:32 ` David Miller
2010-02-06 6:28 ` Christian Kujau
2010-02-06 6:43 ` David Miller
2010-02-08 21:46 ` 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=20100208214619.GB2814@think \
--to=chris.mason@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@nerdbynature.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