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: Sat, 18 Apr 2009 19:05:57 -0700 From: Joe Perches <joe@...ches.com> To: Frederic Weisbecker <fweisbec@...il.com> Cc: Rusty Russell <rusty@...tcorp.com.au>, Ingo Molnar <mingo@...e.hu>, Sam Ravnborg <sam@...nborg.org>, Steven Rostedt <rostedt@...dmis.org>, Zhaolei <zhaolei@...fujitsu.com>, Tom Zanussi <tzanussi@...il.com>, Li Zefan <lizf@...fujitsu.com>, LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: RFC: introduce struct ksymbol On Sat, 2009-04-18 at 18:09 +0200, Frederic Weisbecker wrote: > The only problem is the end result: > > %pSnosm, %pSno, %pSosm, ... > > One could end up stuck reading such a format, trying > to guess if the developer wanted to print the symbol + > "nosm" or something... > > But since I don't see any point in printing nosm directly after > a symbol... :) You couldn't do that anymore anyway. The %p<TYPE> convention already swallows all alphanumeric characters that immediately follow %p. vsprintf.c line 1043 case FORMAT_TYPE_PTR: str = pointer(fmt+1, str, end, va_arg(args, void *), spec); while (isalnum(*fmt)) fmt++; break; -- 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