| 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: Sun, 8 Nov 2009 13:49:17 -0200 From: André Goddard Rosa <andre.goddard@...il.com> To: Jan Engelhardt <jengelh@...ozas.de> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v4 01/12] vsprintf: factorize "(null)" string On Sun, Nov 8, 2009 at 1:37 PM, Jan Engelhardt <jengelh@...ozas.de> wrote: > > Stripping the humongous Cc list for sanity. > > > On Saturday 2009-11-07 16:16, André Goddard Rosa wrote: > >>Change "<NULL>" to "(null)" and make it a static const char[] hoping that >>the compiler will make null_str a label to a read-only area containing it. > > Hoping? Nah, thanks. :) That's just because I don't always trust gcc blindly. :) >>See: >>http://udrepper.livejournal.com/13851.html > > Ulrich's example already _has_ a variable that is then changed from > const char * to const char[]. Of course doing that will save you the > extra pointer. > But vsprintf.c on the other hand did not have that extra variable to > begin with! Correct, of course! Most relevant reference is the first one: http://people.redhat.com/drepper/dsohowto.pdf part 2.4.2 The others are just related/akin to the topic; interesting nevertheless. > But it is ok nevertheless, and the unification of <NULL> vs > (null) is worthwhile. Thanks, André -- 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