linux-kernel - Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware

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]

Message-Id: <20160318.231626.670272515350508280.davem@davemloft.net>
Date:	Fri, 18 Mar 2016 23:16:26 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	joe@...ches.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next 0/2] Create ancient subdirectories for old
 hardware

From: Joe Perches <joe@...ches.com>
Date: Fri, 18 Mar 2016 19:28:02 -0700

> On Fri, 2016-03-18 at 22:11 -0400, David Miller wrote:
>> From: Joe Perches <joe@...ches.com>
>> Date: Fri, 18 Mar 2016 17:33:29 -0700
>> 
>> > Maybe something like this:
>> > 
>> > Old, rare, and unsupported hardware should be exposed as ancient.
>> > 
>> > The drivers for these ancient hardwares are generally untested with
>> > current kernels.
>> 
>> Moving drivers has a long term maintainence cost.
>> 
>> If they've moved into drivers/net proper, we have to maintain
>> them there forever.
> 
> I don't doubt that.
> 
> All files are still in drivers/net, just possibly in
> separate subdirectories for easier visibility to
> determine if changes like what were proposed for cxgb
> should actually be done or not.

You don't understand my concern, backporting patches to -stable
releases is more painful if you move the driver anywhere other
than where it has been for years.

I'm not entertaining this idea, sorry Joe.