linux-kernel - Re: [PATCH] use %p for pointers

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Oct 2006 14:33:53 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Nikita Danilov <nikita@...sterfs.com>
cc:	Andreas Schwab <schwab@...e.de>, "H. Peter Anvin" <hpa@...or.com>,
	torvalds@...l.org, linux-kernel@...r.kernel.org,
	Al Viro <viro@....linux.org.uk>
Subject: Re: [PATCH] use %p for pointers

> > > man 3 printf:
> > >
> > >        p      The void * pointer argument is printed in hexadeci-
> > >               mal (as if by %#x or %#lx).
> > >
> > > so %p already has to output '0x',
> > 
> > That is an detail of this particular implementation.
> > 
> > > it's lib/vsprintf.c to blame for non-conforming behavior.
> > 
> > The standard makes it completely implementation defined.
>
>Yes, but POSIX/SUS aside, at least we might make kernel version closer
>to Linux user-level.

I do agree.

#include <stdio.h>
int main(void) {
    return printf("%p %p\n", main, NULL);
}

In glibc will print "0x7555562c (nil)" which seems ok enough.


	-`J'
-- 
-
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/