| 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, 29 Jun 2015 00:54:08 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Julia Lawall <julia.lawall@...6.fr> Cc: "Dilger, Andreas" <andreas.dilger@...el.com>, "devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Drokin, Oleg" <oleg.drokin@...el.com>, "lustre-devel@...ts.lustre.org" <lustre-devel@...ts.lustre.org> Subject: Re: LIBCFS_ALLOC Yeah. You're right. Doing a vmalloc() when kmalloc() doesn't have even a tiny sliver of RAM isn't going to work. It's easier to use libcfs_kvzalloc() everywhere, but it's probably the wrong thing. regards, dan carpenter -- 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