| 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
| ||
|
Message-ID: <CALZhoSSFnfU1oVtUOXF_gA3QjToqT-wtdckbMC43pDXwXZwupg@mail.gmail.com> Date: Tue, 12 Mar 2013 13:34:56 +0800 From: Lei Wen <adrian.wenl@...il.com> To: Tejun Heo <tj@...nel.org> 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 1:24 PM, Tejun Heo <tj@...nel.org> wrote: > On Tue, Mar 12, 2013 at 01:18:01PM +0800, Lei Wen wrote: >> > You're initializing random piece of memory which may contain any >> > garbage and triggering BUG if some bit is set on it. No, you can't do >> > that. debugobj is the right tool for debugging object lifetime issues >> > and is already supported. >> >> The debugobj is not helping on this issue, I have enabled both >> CONFIG_DEBUG_OBJECTS_WORK and CONFIG_DEBUG_OBJECTS. >> But find they didn't report any issue at all. > > It should. No idea why it didn't. Would be interesting to find out > why. No idea about it also... > >> And I am not init random memory, original issue is call init multi-times >> for one structure and that piece of memory already been allocated. >> And __INIT_WORK shouldn't call over random memory, right? > > Memory areas aren't always zero on allocation. Shouldn't work structure be allocated with kzalloc? Thanks, Lei -- 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