netdev - Re: [PATCH net-next] net: NET_VENDOR

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

Message-Id: <20180517.123203.962104853214011861.davem@davemloft.net>
Date:   Thu, 17 May 2018 12:32:03 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...il.com
Cc:     netdev@...r.kernel.org, alexandre.belloni@...tlin.com
Subject: Re: [PATCH net-next] net: NET_VENDOR_MICROSEMI should default ot N

From: David Ahern <dsahern@...il.com>
Date: Thu, 17 May 2018 08:43:30 -0700

> Other ethernet drivers default to N. There is no reason for Microsemi
> to default to y. I believe Linus has set the bar at a feature that cures
> cancer can be enabled by default. [1]
> 
> [1] https://lkml.org/lkml/2010/3/2/366
> 
> Signed-off-by: David Ahern <dsahern@...il.com>

For "drivers" yes, those should default to N.  But for vendor guards
like this, they should default to Y.