netdev - Re: possible bug in latest network tree

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAM_iQpWHT-iMYm++CroUZO9Czih7xOnbDkauhTP8qhtqHLbpag@mail.gmail.com>
Date:	Thu, 31 Mar 2016 15:34:40 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	"Light, John J" <john.j.light@...el.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: possible bug in latest network tree

On Wed, Mar 30, 2016 at 2:05 PM, Light, John J <john.j.light@...el.com> wrote:
>
> Maybe the problem is that the default shouldn't be to a TCP value, but should be a 'transport' value.
>

The code is fine because net->ipv4 is always there, it doesn't
depend on any CONFIG, so it is safe for dccp to use too, although
I agree it is a bit ugly.