All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Christian Borntraeger <CBORNTRA@de.ibm.com>
Cc: ext3-users@redhat.com, linux-kernel@vger.kernel.org,
	Carsten Otte <COTTE@de.ibm.com>,
	Tom Rini <trini@kernel.crashing.org>
Subject: Re: BUG: Assertion failure with ext3-0.95 for 2.4.7
Date: Thu, 09 Aug 2001 11:58:46 -0700	[thread overview]
Message-ID: <3B72DD66.A6F65247@zip.com.au> (raw)
In-Reply-To: <OF5E574EE5.AF3B6F6F-ONC1256AA2.0026D8D3@de.ibm.com>

Christian Borntraeger wrote:
> 
> Hello ext3-users,
> 
> I tested ext3 on a Linux for S/390 with several stress and benchmark test
> tests and faced a kernel bug message.
> The console showed the following output:
> 
> Message from syslogd@boeaet34 at Fri Aug  3 11:34:16 2001 ...
> boeaet34 kernel: Assertion failure in journal_forget() at
> transaction.c:1184: "!
> jh->b_committed_data"
> 

Simple bug, subtle symptoms.  Could you please retest 0.9.5
with this patch?  Thanks.

--- ext3-0_9_5/fs/ext3/inode.c	Mon Jul 30 05:46:12 2001
+++ ext3/fs/ext3/inode.c	Thu Aug  9 00:03:34 2001
@@ -1522,7 +1523,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;
 

Now, if all on-disk structures were defined in terms of something
like

	struct disk32 {
		u32 x;
	}

then these things wold never happen - the compiler would catch
it.

-

  parent reply	other threads:[~2001-08-09 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  8:46 BUG: Assertion failure with ext3-0.95 for 2.4.7 Christian Borntraeger
2001-08-08  9:26 ` Arjan van de Ven
2001-08-08 15:16 ` Tom Rini
2001-08-09 18:58 ` Andrew Morton [this message]
2001-08-10 17:44   ` Tom Rini
2001-08-10 18:09     ` Andrew Morton
2001-08-10 18:10       ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2001-08-08  9:36 Christian Borntraeger
2001-08-08 14:38 Christian Borntraeger
2001-08-08 15:27 ` Tom Rini
2001-08-09  9:26 Christian Borntraeger
2001-08-13  6:53 Christian Borntraeger
2001-08-14  8:34 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=3B72DD66.A6F65247@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=CBORNTRA@de.ibm.com \
    --cc=COTTE@de.ibm.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.