netdev - Re: size of data_segs_[in|out] and segs

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: <e4365bea-e591-3041-14f8-4ecae7e91f75@psc.edu>
Date:	Tue, 9 Aug 2016 15:15:59 -0400
From:	rapier <rapier@....edu>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: size of data_segs_[in|out] and segs_[in|out]



On 8/9/16 3:04 PM, David Miller wrote:
> From: rapier <rapier@....edu>
> Date: Tue, 9 Aug 2016 13:17:59 -0400
>
>> I cannot deny that would be a problem but conversely, those
>> applications are currently in a position where they may be depending
>> on inaccurate data. I'm not advocating breaking things for the sake of
>> breaking things but my feeling is that this will eventually need to be
>> addressed. Since the segs datastructure is a relatively recent
>> addition it might make sense to make that change now before it's even
>> more baked in to other applications.
>
> Changing the size or position of these data structure members is
> simply not an option.  It is locked into stone, and a permanent
> ABI which we cannot change.
>
> Please stop discussing as if changing this is a possibility.

I apologize, I wasn't aware of the constraints on this. There are other 
solutions available and I'll focus on those.