| 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
| ||
|
Date: Mon, 11 Mar 2013 23:13:03 -0700 From: Tejun Heo <tj@...nel.org> To: Lei Wen <adrian.wenl@...il.com> Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, leiwen@...vell.com, wwang27@...vell.com Subject: Re: workqueue panic in 3.4 kernel On Tue, Mar 12, 2013 at 02:01:16PM +0800, Lei Wen wrote: > I see... > How about only check those workqueue structure not on stack? > For current onstack usage is rare, and should be easier to check with. No, kzalloc is not required. The memory area can come from any source. If you're interested in improving the debug situation, please stop trying to do something impossible (you can't track lifetime of random memory area without extra bookkeeping) try to find out why debugobj didn't detect it (did you even enable it? either via CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT or "debug_objects" boot param). -- tejun -- 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/
Powered by blists - more mailing lists