linux-kernel - Re: [PATCH] vsprintf: do not append unset Scope ID to IPv6

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:	Wed, 03 Feb 2016 23:09:16 +0100
From:	Daniel Borkmann <daniel@...earbox.net>
To:	Joe Perches <joe@...ches.com>,
	"Jason A. Donenfeld" <Jason@...c4.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux@...musvillemoes.dk, andriy.shevchenko@...ux.intel.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vsprintf: do not append unset Scope ID to IPv6

On 02/03/2016 10:47 PM, Joe Perches wrote:
> On Wed, 2016-02-03 at 22:14 +0100, Jason A. Donenfeld wrote:
>> The idea here is to be able to printk a sockaddr_in6, and have it show
>> something that looks like what the user would naturally pass to
>> getaddrinfo(3), which is entirely complete.
>>
>> However, I could be convinced that this kind of behavior belongs in
>> it's own flag. Maybe I'll cook up a flag for that instead.
>
> I think that'd be best.

Agreed.

> Maybe using something like %pISG for this that
> would optionally show these flow and scope values
> only when non-zero.
>
> Something like:

Looks good to me, having this as a single generic option seems
even cleaner.

Thanks!