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: Thu, 20 Oct 2005 22:44:47 +0200 [thread overview]
Message-ID: <435801BF.90701@vc.cvut.cz> (raw)
In-Reply-To: <4347F3DE.8070505@vc.cvut.cz>
Petr Vandrovec wrote:
> 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.
> 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.
Still no clue, but somebody still writes 0x00000001 here and there around my
inodes :-( This time when I was building 2.6.14-rc5 kernel... Apparently
whenever my old kernel finds that it is going to be replaced it attempts to
boycott build of new kernel.
Linux ppc 2.6.14-rc3-8298 #9 SMP PREEMPT Sun Oct 9 03:45:32 CEST 2005 x86_64
GNU/Linux
slab error in cache_free_debugcheck(): cache `size-64': double free, or memory
outside object was overwritten
Call Trace:<ffffffff8017230a>{cache_free_debugcheck+378}
<ffffffff8017376c>{kfree+220}
<ffffffff801aaafe>{clear_inode+174} <ffffffff801aaba8>{dispose_list+104}
<ffffffff801aaffa>{prune_icache+426}
<ffffffff801ab067>{shrink_icache_memory+23}
<ffffffff80176185>{shrink_slab+229} <ffffffff801776bd>{balance_pgdat+589}
<ffffffff80371474>{_spin_lock_irqsave+36} <ffffffff80177937>{kswapd+311}
<ffffffff80155070>{autoremove_wake_function+0}
<ffffffff80155070>{autoremove_wake_function+0}
<ffffffff801356dd>{schedule_tail+77} <ffffffff8010fd92>{child_rip+8}
<ffffffff80177800>{kswapd+0} <ffffffff8010fd8a>{child_rip+0}
ffff8100005e7c38: redzone 1: 0x170fc2a5, redzone 2: 0x1.
Petr
>> 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.
prev parent reply other threads:[~2005-10-20 20:44 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
2005-10-20 20:44 ` Petr Vandrovec [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=435801BF.90701@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