From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc2-almost-rc3, ext3 and memory corruption
Date: Sat, 08 Oct 2005 18:29:18 +0200 [thread overview]
Message-ID: <4347F3DE.8070505@vc.cvut.cz> (raw)
In-Reply-To: <20051001030027.GA8784@vana.vc.cvut.cz>
Petr Vandrovec wrote:
> Hello,
> I was so happy that 2.6.13-rc3 was released that I tried to grab it,
> and while I was doing that, box said:
>
> Slab corruption: start=ffff8100005e5bf8, len=96
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<ffffffff801ec42d>](journal_remove_journal_head+0x6d/0xb0)
> 000: 6b 6b 6b 6b 6b 6b 6b 6b 01 00 00 00 6b 6b 6b 6b
> Prev obj: start=ffff8100005e5b80, len=96
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<ffffffff801ec42d>](journal_remove_journal_head+0x6d/0xb0)
> 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> Next obj: start=ffff8100005e5c70, len=96
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<ffffffff801ec42d>](journal_remove_journal_head+0x6d/0xb0)
> 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Hello,
so I've enabled JBD-DEBUG, and unfortunately somebody corrupted inode instead
of journal head this time :-( But corruption looks same - somebody wrote 32bit
value 1 somewhere it should not... Does anybody have something like
CONFIG_DEBUG_PAGE_ALLOC for x86-64?
Slab corruption: start=ffff8100005e7c00, len=976
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff801aa690>](destroy_inode+0x30/0x50)
080: 01 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Prev obj: start=ffff8100005e7818, len=976
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff801aa690>](destroy_inode+0x30/0x50)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
ppc:~$ uname -a
Linux ppc 2.6.14-rc3-dd72 #1 SMP PREEMPT Tue Oct 4 21:12:16 CEST 2005 x86_64
GNU/Linux
ppc:~$
This time I was not doing anything special, just building new kernel & browsing web.
Thanks,
Petr Vandrovec
> Box in question has single Athlon64 processor, runs SMP PREEMPT kernel
> with almost all debugging options set (but not CONFIG_JBD_DEBUG). Box
> has 2GB of ECC RAM. Root filesystem is on pata disk connected to the
> pata port on Promise's 20378 (using sata_promise). Disk with git repository
> is plugged to pata port on Via's VT8237. Kernel's configuration is
> at http://platan.vc.cvut.cz/vana_at_home_config.txt, dmesg at
> http://platan.vc.cvut.cz/vana_at_home_dmesg.txt.
next prev parent reply other threads:[~2005-10-08 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 3:00 2.6.13-rc2-almost-rc3, ext3 and memory corruption Petr Vandrovec
2005-10-08 16:29 ` Petr Vandrovec [this message]
2005-10-20 20:44 ` Petr Vandrovec
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=4347F3DE.8070505@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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