From: Chris Mason <chris.mason@oracle.com>
To: Sean Reifschneider <jafo@tummy.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrstress caused kernel oops after 8-ish days.
Date: Tue, 27 Apr 2010 07:46:28 -0400 [thread overview]
Message-ID: <20100427114628.GC6513@think> (raw)
In-Reply-To: <4BD6C712.6090202@tummy.com>
On Tue, Apr 27, 2010 at 05:14:26AM -0600, Sean Reifschneider wrote:
> I ported my zfsstress program over to btrfs, and started running it on
> a test machine a few weeks ago. See here for more information and a link
> to the program:
>
> http://www.tummy.com/journals/entries/jafo_20100418_124309
Interesting, I'll take a look.
>
> dmesg output of oops below.
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000075
> IP: [<ffffffff810e380f>] page_cache_sync_readahead+0x15/0x3a
This oops is fixed in later kernels, and it's why things stopped.
-chris
next prev parent reply other threads:[~2010-04-27 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 11:14 btrstress caused kernel oops after 8-ish days Sean Reifschneider
2010-04-27 11:46 ` Chris Mason [this message]
2010-04-28 1:30 ` Sean Reifschneider
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=20100427114628.GC6513@think \
--to=chris.mason@oracle.com \
--cc=jafo@tummy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox