| 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: <2f86c2480907270849x65af933fnc58d3cb243649b1f@mail.gmail.com> Date: Mon, 27 Jul 2009 11:49:39 -0400 From: Benjamin Blum <bblum@...gle.com> To: Li Zefan <lizf@...fujitsu.com> Cc: linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org, akpm@...ux-foundation.org, serue@...ibm.com, menage@...gle.com Subject: Re: [PATCH 3/6] Quick vmalloc vs kmalloc fix to the case where array size is too large On Mon, Jul 27, 2009 at 1:14 AM, Li Zefan<lizf@...fujitsu.com> wrote: > Ben Blum wrote: >> Quick vmalloc vs kmalloc fix to the case where array size is too large >> >> Separates all pidlist allocation requests to a separate function that judges >> based on the requested size whether or not the array needs to be vmalloced or >> can be gotten via kmalloc, and similar for kfree/vfree. Should be replaced >> entirely with a kernel-wide solution to this general problem. >> >> Depends on cgroup-pidlist-namespace.patch, cgroup-procs.patch >> >> Signed-off-by: Ben Blum <bblum@...gle.com> >> > > We'll either use flex_array or implement Paul's proposal, so I think > we can drop this patch? > > Depending how long they'll take, yes. This is meant to be an intermediate correctness patch. -- 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