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: Tue, 4 Mar 2008 11:32:20 +0100 From: Ingo Molnar <mingo@...e.hu> To: Suresh Siddha <suresh.b.siddha@...el.com> Cc: Christoph Hellwig <hch@...radead.org>, hpa@...or.com, tglx@...utronix.de, andi@...stfloor.org, linux-kernel@...r.kernel.org, Arjan van de Ven <arjan@...ux.intel.com> Subject: Re: [patch 2/2] x86, fpu: lazy allocation of FPU area - v3 * Suresh Siddha <suresh.b.siddha@...el.com> wrote: > On Mon, Mar 03, 2008 at 08:20:12PM -0500, Christoph Hellwig wrote: > > On Mon, Mar 03, 2008 at 03:02:46PM -0800, Suresh Siddha wrote: > > > + /* > > > + * Memory allocation at the first usage of the FPU and other state. > > > + */ > > > + if (!tsk->thread.xstate) > > > + tsk->thread.xstate = kmem_cache_alloc(task_xstate_cachep, GFP_KERNEL); > > > > Also don't we need some kind of error handling here? > > Currently it uses SLAB_PANIC. but SLAB_PANIC only covers kmem_cache_create() failures. kmem_cache_alloc() can fail (return NULL) and not handling it is a bug. Ingo -- 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