mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Daniel Fenert <daniel@fenert.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Michelle Konzack <linux4michelle@freenet.de>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: Is there some bug in ext3 in 2.4.25?
Date: 05 Mar 2004 14:25:13 +0000	[thread overview]
Message-ID: <1078496713.14033.53.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403051048160.2678-100000@dmt.cyclades>

Hi,

On Fri, 2004-03-05 at 14:06, Marcelo Tosatti wrote:

> This sounds like memory corruption (which could be caused by a misbehaving
> driver or by flaky hardware) because transaction->t_ilist is not used at
> all by the kernel code. Did this box run stable with other kernels?

Sounds like bad memory to me.  The only other report of this I've seen
was at

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115935

and that machine didn't pass memtest86.

> Stephen, Andrew, any idea how can transaction->t_ilist become not NULL?

Bad hardware is about the only way I can think of.  If it was a random
kernel memory scribble, you'd expect it to show up in other places too:
the transaction struct is a very very long-lived struct, you wouldn't
expect it to be the only place to show up slab corruptions.

Cheers,
 Stephen


  parent reply	other threads:[~2004-03-05 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  6:50 Daniel Fenert
2004-03-04  7:03 ` Daniel Fenert
2004-03-05 14:06 ` Marcelo Tosatti
2004-03-05 14:14   ` Michael Frank
2004-03-05 14:26     ` Stephen C. Tweedie
2004-03-05 14:25   ` Stephen C. Tweedie [this message]
2004-03-08 13:44     ` Daniel Fenert
2004-04-02 10:20     ` Daniel Fenert
2004-04-02 10:37       ` Stephen C. Tweedie

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=1078496713.14033.53.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=daniel@fenert.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux4michelle@freenet.de \
    --cc=marcelo.tosatti@cyclades.com \
    /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®