netdev - Re: [PATCH v3 net-next 3/3] rds: Extend RDS API for IPv6 support

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:   Fri, 13 Jul 2018 16:31:26 -0700
From:   Santosh Shilimkar <santosh.shilimkar@...cle.com>
To:     David Miller <davem@...emloft.net>
Cc:     ka-cheong.poon@...cle.com, netdev@...r.kernel.org,
        sowmini.varadhan@...cle.com, rds-devel@....oracle.com
Subject: Re: [PATCH v3 net-next 3/3] rds: Extend RDS API for IPv6 support

On 7/13/2018 4:27 PM, David Miller wrote:
> From: Santosh Shilimkar <santosh.shilimkar@...cle.com>
> Date: Fri, 13 Jul 2018 15:00:59 -0700
> 
>> Ofcourse any application built using upstream header and
>> using SO_RDS_TRANSPORT will break but since this particular
>> option was added for special case(application wants to
>> upfront select transport instead letting bind figure it out),
>> our hope its not used by other application(s).
> 
> We can't let people have different UAPIs from upstream on a whim like
> this then change the already released upstream UAPI to match.
> 
> Please take this into consideration when making changes in the future.
>
Will not be repeated in future.

> I'm not allowing this upstream UAPI break, sorry.
> 
Ok Dave !!

Regards,
Santosh