All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Eric Whitney <eric.whitney@hp.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: PROBLEM: oops when running fsstress against compressed btrfs filesystem
Date: Fri, 12 Dec 2008 09:25:58 -0500	[thread overview]
Message-ID: <1229091958.11620.3.camel@think.oraclecorp.com> (raw)
In-Reply-To: <493860B8.4040309@hp.com>

On Thu, 2008-12-04 at 17:59 -0500, Eric Whitney wrote:
> Chris:
> 
> I'm consistently getting oopses when running fsstress against both 
> single and multiple device compressed btrfs filesystems using kernels 
> built from the current btrfs-unstable.
> 

Sorry it took so long to reply to this one, I wanted to get the new csum
code nailed down before I asked you to retest.  I've changed big parts
of the compressed IO submission path, and I'd like to see if this bug is
still a problem.

-chris



  reply	other threads:[~2008-12-12 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 22:59 PROBLEM: oops when running fsstress against compressed btrfs filesystem Eric Whitney
2008-12-12 14:25 ` Chris Mason [this message]
2008-12-12 17:09   ` Chris Mason
2008-12-15 18:43 ` Chris Mason

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=1229091958.11620.3.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=eric.whitney@hp.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.