| 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: Fri, 02 Oct 2009 11:19:17 +0100 From: "Jan Beulich" <JBeulich@...ell.com> To: <adaplas@...il.com>, <ilya.yanok@...il.com> Cc: <linux-kernel@...r.kernel.org> Subject: commit 68e5e9d734503695915734e50e9427624cf8f3b2 (Re: vfb: make virtual framebuffer mmapable) Is there any particular reason why this change uses vmalloc_32() rather than simply vmalloc()? I can't see why the underlying physical address width would matter here in any way... Thanks, Jan -- 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