linux-kernel - Re: [PATCH] net-sysfs: Report link speed only when possible

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:	Mon, 16 Jun 2014 09:32:35 +0200
From:	Michal Privoznik <mprivozn@...hat.com>
To:	David Miller <davem@...emloft.net>
CC:	jiri@...nulli.us, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] net-sysfs: Report link speed only when possible

On 13.06.2014 22:03, David Miller wrote:
> From: Michal Privoznik <mprivozn@...hat.com>
> Date: Fri, 13 Jun 2014 11:19:51 +0200
>
>> So if I were developing brand new application I could say: I'm
>> dropping all this workaround code and have it clean and require say
>> 3.16 kernel at least.
>
> Then your application wouldn't be usable on %99 of systems for a long
> long time.
>

How come? The application is going to be usable for as long as 
library/kernel APIs won't change. Or until the time a new regression is 
introduced and fix is rejected. Speaking of which - long long time 
applications *are* broken now. This patch is combining the good from 
both worlds: old applications are fixed, new applications doesn't have 
to learn anything new.

> I don't think this is the right tradeoff at all.
>

Neither is keeping things broken.

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/