linux-kernel - Re: [net-next] seg6: add support for optional attributes during behavior construction

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]

Date:   Tue, 31 Mar 2020 03:32:11 +0200
From:   Stefano Salsano <stefano.salsano@...roma2.it>
To:     David Miller <davem@...emloft.net>
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
        dav.lebrun@...il.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, leon@...nel.org, ast@...nel.org,
        daniel@...earbox.net, kafai@...com, songliubraving@...com,
        yhs@...com, andriin@...com, bpf@...r.kernel.org,
        paolo.lungaroni@...t.it, ahmed.abdelsalam@...i.it
Subject: Re: [net-next] seg6: add support for optional attributes during
 behavior construction

Il 2020-03-31 02:49, David Miller ha scritto:
> From: Stefano Salsano <stefano.salsano@...roma2.it>
> Date: Tue, 31 Mar 2020 01:23:48 +0200
> 
>> Of course a new application (e.g. iproute2, pyroute) using a new optional
>> parameter will not work on older kernels, but simply because the new parameter
>> is not supported. It will not work even without our proposed patch.
>>
>> On the other hand, we think that the solution in the patch is more backward
>> compatible. Without the patch, if we define new attributes, old applications
>> (e.g. iproute2 scripts) will not work on newer kernels, while with the optional
>> attributes approach proposed in the patch they will work with no issues !
> 
> Translation: You want to add backwards compatibility problems because
> otherwise you'll have to add backwards compatibility problems.

no this is not the correct translation :-) we do not want to add any 
backward compatility problem

we need to add a number of new parameters, if we keep the current 
approach these parameters will be mandatory and we will have backward 
compatibility problems: old applications will not work with new kernels

if we are allowed to add optional parameters, old applications and new 
applications will be able to work with old kernels and new kernels in 
any combination

> Sorry, I'm still not convinced.
> 
> You must find another way to achieve your objective.


-- 
*******************************************************************
Stefano Salsano
Professore Associato
Dipartimento Ingegneria Elettronica
Universita' di Roma Tor Vergata
Viale Politecnico, 1 - 00133 Roma - ITALY

http://netgroup.uniroma2.it/Stefano_Salsano/

E-mail  : stefano.salsano@...roma2.it
Cell.   : +39 320 4307310
Office  : (Tel.) +39 06 72597770 (Fax.) +39 06 72597435
*******************************************************************