From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: 2.6.23-rc6-git3 (not -git4): reiserfs bug
Date: Thu, 13 Sep 2007 12:56:32 -0700 [thread overview]
Message-ID: <20070913125632.885563da.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070913125448.e71a0b11.randy.dunlap@oracle.com>
On Thu, 13 Sep 2007 12:54:48 -0700 Randy Dunlap wrote:
> on x86_64, 2 CPU + HT, 4 GB RAM:
>
> reiserfs with blocksize of 1 KB, data=ordered
>
>
> [ 9828.242431] ------------[ cut here ]------------
> [ 9828.247056] kernel BUG at fs/reiserfs/journal.c:531!
> [ 9828.252017] invalid opcode: 0000 [1] SMP
> [ 9828.256070] CPU 0
> [ 9828.258105] Modules linked in: reiserfs loop
> [ 9828.262428] Pid: 16555, comm: pdflush Not tainted 2.6.23-rc6-git3 #1
~~~~~~~~~~~~~~~~~~
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-09-13 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:54 2.6.23-rc6-git4: " Randy Dunlap
2007-09-13 19:56 ` Randy Dunlap [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=20070913125632.885563da.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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
all inboxes | Powered by JetHome®