public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: mroconnor@oel.state.nj.us
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel bug in file-item.c
Date: Tue, 28 Apr 2009 15:23:53 -0400	[thread overview]
Message-ID: <1240946633.15136.55.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49F73F69.4010205@oel.state.nj.us>

On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
> I have had two 'kernel bug' issues today both referencing file-item.c.
> The first oops happened when i was cp'ing from and external HD(ext3) to
> and ext3 partition. The second happened during boot up. I have attached
> them both.
> 
> Im using btrfs that was merged into my kernel yesterday.
> 
> plain text document attachment (btrfs_bug_1)
> Apr 28 10:55:10 cosmo2 ------------[ cut here ]------------
> Apr 28 10:55:10 cosmo2 kernel BUG at fs/btrfs/file-item.c:494!

Well, I think I see the bug.  It looks like we want to do

-        if (key->offset < bytenr && csum_end <= end_byte) {
+        if (key->offset <= bytenr && csum_end <= end_byte) {

in truncate_one_csum.  But I need to test that here for a bit and send
you a patch.

-chris



  reply	other threads:[~2009-04-28 19:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 17:39 kernel bug in file-item.c Marc R. O'Connor
2009-04-28 19:23 ` Chris Mason [this message]
2009-04-28 19:30   ` Marc R. O'Connor
2009-04-29 16:04   ` Marc R. O'Connor
2009-04-29 17:53     ` Chris Mason
2009-04-29 18:21       ` Marc R. O'Connor
2009-04-29 18:30         ` Chris Mason
2009-04-29 18:38           ` Marc R. O'Connor
2009-04-29 18:40             ` Chris Mason
2009-04-29 18:46               ` Marc R. O'Connor
2009-04-29 18:50               ` Zach Brown
2009-04-29 19:04                 ` Marc R. O'Connor
2009-04-30  7:23                   ` Dmitri Nikulin
2009-04-29 19:32               ` Tracy Reed
2009-04-30  9:08                 ` Paul Komkoff
2009-04-30 16:54                   ` Tracy Reed
2009-05-01  2:13                     ` Dmitri Nikulin

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=1240946633.15136.55.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mroconnor@oel.state.nj.us \
    /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