From: "Szonyi Calin" <sony@etc.utt.ro>
To: <akpm@digeo.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Bug: slab corruption in 2.5.67-mm1
Date: Mon, 14 Apr 2003 20:01:18 +0300 (EEST) [thread overview]
Message-ID: <48500.194.138.39.56.1050339678.squirrel@webmail.etc.utt.ro> (raw)
In-Reply-To: <20030412181805.1b90bee8.akpm@digeo.com>
Andrew Morton said:
> J Sloan <joe@tmsusa.com> wrote:
>>
>> This may be of interest -
>>
>> kernel: 2.5.67-mm1
>>
>> Linux distro: Red Hat 8.0 + updates
>>
>> Hardware:
>> Celeron 1.2 Ghz on Intel Motherboard
>> 512 MB RAM, 2x e100 ethernet
>
> whoa. Uniprocessor.
>
>> ---- snip ----
>> Freeing unused kernel memory: 312k freed
>> EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,3), internal journal
>> Adding 514072k swap on /dev/hda2. Priority:42 extents:1
>> kjournald starting. Commit interval 5 seconds
>> EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,1), internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> Slab corruption: start=dfa2f320, expend=dfa2f97f, problemat=dfa2f328
>> Data: ********6A
>
> Yes, this means that someone ran put_task_struct() against an
> already-freed task_struct. There's some deubg code in -mm which is
> supposed to trap this, but it obviously didn't trigger for some reason.
>
> Until someone finds a way to reproduce this we're a bit stuck. A code
> audit may find it.
FYI
Same thing happend on my machine *once*, in the same place
(i.e mounting root fs -- JFS) but i forgot the full report on my home
machine :-(.
Kernel 2.5.67 mm1 compiled by gcc 3.2.2 and booted with "debug"
on kernel command line. Couldn't reproduce it :-(
Machine: Duron 700 MHz, 256 M RAM, chipset Via KT133, ATI Radeon VE QY
graphics card, CS4239 sound card, no ethernet.
Distribution Slackware 8.1 + updates.
Calin
--
# fortune
fortune: write error on /dev/null --- please empty the bit bucket
-----------------------------------------
This email was sent using SquirrelMail.
"Webmail for nuts!"
http://squirrelmail.org/
prev parent reply other threads:[~2003-04-14 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 22:05 J Sloan
2003-04-12 23:24 ` Joshua Kwan
2003-04-12 23:47 ` J Sloan
2003-04-13 1:18 ` Andrew Morton
2003-04-14 17:01 ` Szonyi Calin [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=48500.194.138.39.56.1050339678.squirrel@webmail.etc.utt.ro \
--to=sony@etc.utt.ro \
--cc=akpm@digeo.com \
--cc=linux-kernel@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®