netdev - Re: [PATCH net-next 3/3] Move shared tcp code to net/ipv4v6shared

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 4 Oct 2017 10:57:42 +0200
From:   Richard Siegfried <richard_siegfried@...temli.org>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>, yoshfuji@...ux-ipv6.org,
        kuznet@....inr.ac.ru
Subject: Re: [PATCH net-next 3/3] Move shared tcp code to net/ipv4v6shared

On 04/10/17 03:32, Stephen Hemminger wrote:
> The name ipv4v6_shared is longer than it needs to be maybe ip or ip_common
Well ip_common sounds nice.

But I don't fully understand what this means for the current situation.
I could do a v2, but would that make any sense since Dave and Eric
already said "no" to the whole concept.

Would it change anything to keep the tcp directory in net/ipv4/ (only
1/3 and 2/3)?

Download attachment "signature.asc" of type "application/pgp-signature" (530 bytes)