| 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
| ||
|
Message-Id: <1225307615.5269.379.camel@localhost> Date: Wed, 29 Oct 2008 12:13:34 -0700 From: Joe Perches <joe@...ches.com> To: David Miller <davem@...emloft.net> Cc: harvey.harrison@...il.com, netdev@...r.kernel.org Subject: Re: oh crap... On Wed, 2008-10-29 at 11:31 -0700, David Miller wrote: > From: Joe Perches <joe@...ches.com> > Date: Wed, 29 Oct 2008 11:16:54 -0700 > > On Wed, 2008-10-29 at 10:24 -0700, Harvey Harrison wrote: > > > Putting a modifier after the format specifier seems a little strange to me. > > Harvey, please remember the whole %p<foo> concept is based on > > modifier after format specifier. > I don't think there is any such strict rule, or even that we'd > want to enforce that. Of course there's a strict rule. "%<flags>p" is a normal format conversion specifier. It takes a pointer as its argument. Character(s) immediately after the pointer conversion specifier "p" may be linux-specific format modifiers. > There is nothing wrong with saying something like %pI6 where > the "I" signifies "internet address in 'natural' form" and > "6" is the 'modifier' which you love so much which means > "oh btw, it's ipv6" True enough. 6 and I6 are both modifiers. I have been doodling with sparse to verify the pointer types. I just want a simple rule: char after "%<flag>p" specifies pointer type. Ideally it would be: 4: __be32 * 6: struct in6_addr * R: struct resource * M: char * cheers, Joe -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists