All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Christian Borntraeger <CBORNTRA@de.ibm.com>
Cc: ext3-users@redhat.com, linux-kernel@vger.kernel.org,
	arjanv@redhat.com, sct@redhat.com, trini@kernel.crashing.org,
	Carsten Otte <COTTE@de.ibm.com>
Subject: Re: Debugging help: BUG: Assertion failure with ext3-0.95 for 2.4.7
Date: Thu, 9 Aug 2001 17:22:46 +0100	[thread overview]
Message-ID: <20010809172246.B20408@redhat.com> (raw)
In-Reply-To: <OFA546F20C.78C10EBF-ONC1256AA3.0052D4C2@de.ibm.com>
In-Reply-To: <OFA546F20C.78C10EBF-ONC1256AA3.0052D4C2@de.ibm.com>; from CBORNTRA@de.ibm.com on Thu, Aug 09, 2001 at 05:24:05PM +0200

Hi,

On Thu, Aug 09, 2001 at 05:24:05PM +0200, Christian Borntraeger wrote:
> 
> Hello ext3-developers,
> 
> Just to summarize, I reported a kernel bug message with ext3 on S/390 in
> transaction.c. I was able to reproduce it with a ext3 on LVM  and on MD.
> Tom Rini reported a similar problem on PPC. (both big endian). I have sent
> a backtrace and with jbd-debug set to 5 I was not able to reproduce the
> problem until now.

Thanks.  I think it's due to a missing endian-conversion in
ext3_clear_blocks().  Could you try the patch below?

Cheers,
 Stephen


Index: fs/ext3/inode.c
===================================================================
RCS file: /cvsroot/gkernel/ext3/fs/ext3/inode.c,v
retrieving revision 1.63
diff -u -r1.63 inode.c
--- fs/ext3/inode.c	2001/07/30 12:46:12	1.63
+++ fs/ext3/inode.c	2001/08/09 16:19:29
@@ -1522,7 +1522,7 @@
 	 * AKPM: turn on bforget in journal_forget()!!!
 	 */
 	for (p = first; p < last; p++) {
-		u32 nr = *p;
+		u32 nr = le32_to_cpu(*p);
 		if (nr) {
 			struct buffer_head *bh;
 

  reply	other threads:[~2001-08-09 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 15:24 Debugging help: BUG: Assertion failure with ext3-0.95 for 2.4.7 Christian Borntraeger
2001-08-09 16:22 ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-10  7:00 Christian Borntraeger

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=20010809172246.B20408@redhat.com \
    --to=sct@redhat.com \
    --cc=CBORNTRA@de.ibm.com \
    --cc=COTTE@de.ibm.com \
    --cc=arjanv@redhat.com \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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.