linux-kernel - Re: [sched-devel/latest] WARNING: at mm/slub.c:2443

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: <200804232015.27257.elendil@planet.nl>
Date:	Wed, 23 Apr 2008 20:15:26 +0200
From:	Frans Pop <elendil@...net.nl>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	"Pete Zaitcev" <zaitcev@...hat.com>, "Ingo Molnar" <mingo@...e.hu>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	gregkh@...e.de, "Christoph Lameter" <clameter@....com>
Subject: Re: [sched-devel/latest] WARNING: at mm/slub.c:2443

On Wednesday 23 April 2008, Pekka Enberg wrote:
> Well, a race in mon_text_release() after the kmem_cache_free() loop
> and the call to kmem_cache_destroy() but looks like that can't happen
> either. Frans, is this easily triggerable? If so, can you try with
> CONFIG_SLAB and CONFIG_DEBUG_SLAB enabled instead?

Not really. I've only seen it once two days ago and not at all today while I 
was doing the traces for the scheduling issue.

I can give it a go, but I'm not yet ready to switch to current git on this 
box for longer periods (although so far I've actually had less issues than 
with .24-rc1; fingers crossed). If I get anything I'll follow up.
--
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/