linux-kernel - Re: [bug] SLOB crash, 2.6.24-rc2

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: <20071114.143938.23516450.davem@davemloft.net>
Date:	Wed, 14 Nov 2007 14:39:38 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	mpm@...enic.com, rjw@...k.pl, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org
Subject: Re: [bug] SLOB crash, 2.6.24-rc2

From: Ingo Molnar <mingo@...e.hu>
Date: Wed, 14 Nov 2007 20:05:01 +0100

> the bug went away - and the only thing i did was a networking config 
> tweak. So maybe something in networking corrupts memory?

This wouldn't surprise me at all.

I think we can make some headway on this bug, the next time
you trigger it, if the list debugging was a little less terse.

For example, a backtrace and perhaps even feeding the bad list
pointers in question to the SLAB/SLUB debug helpers that can
identify a kmem cache from a given pointer would help.

Thanks.
-
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/