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: Wed, 15 Oct 2008 16:31:19 -0400 From: Arjan van de Ven <arjan@...radead.org> To: Jiri Slaby <jirislaby@...il.com> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: GIT head no longer boots on x86-64 On Wed, 15 Oct 2008 17:33:42 +0200 Jiri Slaby <jirislaby@...il.com> wrote: > Users usually do > is_vmalloc_addr(a) ? vfree(a) : kfree(a); > Even there it makes more sense to me. > I would like to point out that I greatly dislike any and all such abuses. Either you vmalloc something or you kmalloc it. Doing it dynamic with no way to tell? Horrible. (in fact I might do a patch in the opposite direction; have vmalloc() be fancy and internally try kmalloc first, if it fails, then do the expensive stuff) but really, you need to know what you allocated. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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