linux-kernel - Re: 2.6.19-rc6-mm2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <17780.52337.767875.963882@cse.unsw.edu.au>
Date:	Tue, 5 Dec 2006 12:33:37 +1100
From:	Neil Brown <neilb@...e.de>
To:	Jiri Kosina <jikos@...os.cz>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc6-mm2

On Wednesday November 29, jikos@...os.cz wrote:
> On Tue, 28 Nov 2006, Andrew Morton wrote:
> 
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc6/2.6.19-rc6-mm2/
> 
> md-change-lifetime-rules-for-md-devices.patch gives me the following early 
> during boot (first WARNING() inside __mutex_lock_slowpath(), then BUG at 
> __mutex_lock_slowpath(), just after that slab corruption).
> 
> When I revert md-change-lifetime-rules-for-md-devices.patch, everything 
> seems to go fine (this machine does use neither LVM nor RAID, but the 
> kernel has DM compiled in).
> 
> Config is at http://www.jikos.cz/jikos/junk/.config_md
> 
>  WARNING at kernel/mutex.c:132 __mutex_lock_common()
>   [<c0103d70>] dump_trace+0x68/0x1b5
>   [<c0103ed5>] show_trace_log_lvl+0x18/0x2c
>   [<c010445b>] show_trace+0xf/0x11
>   [<c01044cd>] dump_stack+0x12/0x14
>   [<c036e6ba>] __mutex_lock_slowpath+0xa1/0x213
>   [<c0197c7d>] create_dir+0x24/0x1ba
>   [<c0198317>] sysfs_create_dir+0x45/0x5f
>   [<c01ed1fb>] kobject_add+0xce/0x185
>   [<c01ed3c3>] kobject_register+0x19/0x30
>   [<c02e10c6>] md_probe+0x11a/0x124

Very odd.

md_probe is registering a kobject presenting md specific stuff and
that creates a directory called 'md' inside the block device. e.g.
   /sys/block/md0/md
The inode for /sys/block/md0 appear to be non-existent at this point,
which as you are seeing poisoned memory where the inode should be.
This shouldn't happen and I cannot reproduce it.

I notice it says:
                     |
                     v
>  090: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
>  Single bit error detected. Probably bad RAM.
>  Run memtest86+ or a similar memory test tool.

Have you tried running memtest86 ??

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/