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: <20080404202704.84e743d7.akpm@linux-foundation.org> Date: Fri, 4 Apr 2008 20:27:04 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: David Brownell <david-b@...bell.net> Cc: "Kyungmin Park" <kmpark@...radead.org>, "Josh Boyer" <jwboyer@...il.com>, linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org, "Michael Trimarchi" <trimarchimichael@...oo.it>, spi-devel-general@...ts.sourceforge.net, dwmw2@...radead.org, linux-arm-kernel@...ts.arm.linux.org.uk Subject: Re: [PATCH] jffs2 summary allocation On Fri, 4 Apr 2008 19:41:34 -0700 David Brownell <david-b@...bell.net> wrote: > On Friday 04 April 2008, Andrew Morton wrote: > > This problem comes up pretty often. > > Which problem -- kmalloc(BIG)? Or dma(dma-unsafe-mem)? > Or something else? Code needing a large amount of memory, trying to kmalloc it, then getting into trouble, them using vmalloc, then getting into more trouble. This is kernel - order-0 allocations will always be the most robust. -- 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