From: Chris Mason <mason@suse.com>
To: David Boutcher <boutcher@us.ibm.com>
Cc: reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org
Subject: Re: Memory Corruption
Date: 29 Aug 2002 09:40:26 -0400 [thread overview]
Message-ID: <1030628426.17778.337.camel@tiny> (raw)
On Wed, 2002-08-28 at 17:00, David Boutcher wrote:
>
> >On Mon, 2002-08-19 at 12:50, Dave Boutcher wrote:
> >> Hi,
> >>
> >> I'm chasing a wierd memory corruption problem on a ppc64 system. The
> >> first byte of a slab_t structure keeps getting stepped on (zeroed,
> >> actually.) This happens during a testcase that copies a large file
> >> called "junk" between file systems (a mix of ext2 and reiser) on a
> >> 2.4.13 kernel. I know that's REALLY REALLY old, but it's whats in
> >> SuSE's SLES-7 release that we have customers running...
> >
> >Any chance the test case involves renames?
> >
> >-chris
>
> So I posted my problem with memory corruption a few weeks ago....and the
> problem turned out to be a REALLY old/moldy set of userland reiser tools.
> I don't know exactly why that caused memory corruption in the kernel, but
> updating the tools fixed everything right up.
Well, that shouldn't fix it ;-) Which version of reiserfsprogs were you
running before?
Are the filesystems getting checked during boot at all (you would see
reiserfsck messages during boot)?
-chris
next reply other threads:[~2002-08-29 13:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 13:40 Chris Mason [this message]
2002-09-08 17:51 ` [reiserfs-list] Memory Corruption David Boutcher
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 15:31 Memory corruption Geert Uytterhoeven
2002-08-19 16:50 Memory Corruption Dave Boutcher
2002-08-19 20:01 ` Chris Mason
2002-08-28 21:00 ` David Boutcher
2002-08-15 20:26 Memory corruption Dave Boutcher
2002-08-15 20:36 ` Andreas Dilger
2001-01-05 8:33 Memory Corruption Ryan Sizemore
1999-06-22 1:39 Memory corruption Ulf Carlsson
1999-06-30 1:01 ` William J. Earl
1999-06-30 2:47 ` Ulf Carlsson
1999-06-30 22:01 ` William J. Earl
1999-07-01 0:23 ` Ralf Baechle
1999-07-01 0:53 ` William J. Earl
1999-07-01 11:25 ` Harald Koerfgen
1999-07-02 22:41 ` Ralf Baechle
1999-07-06 13:05 ` Ralf Baechle
1999-07-07 21:08 ` Harald Koerfgen
1999-07-08 1:51 ` Warner Losh
1999-07-08 3:12 ` William J. Earl
[not found] ` <37846EE7.EADD9E32@niisi.msk.ru>
1999-07-08 17:56 ` William J. Earl
1999-07-08 10:39 ` Ralf Baechle
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=1030628426.17778.337.camel@tiny \
--to=mason@suse.com \
--cc=boutcher@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-list@namesys.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 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.