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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e0a3f13a-f3cc-8455-8e7d-9c604f8ef4fb@psc.edu>
Date:	Tue, 9 Aug 2016 13:17: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/8/16 7:02 PM, David Miller wrote:
> From: rapier <rapier@....edu>
> Date: Mon, 8 Aug 2016 18:02:29 -0400
>
>> As such, would it be feasible to define these instruments as 64bit
>> instead of 32bit? If so, a cursory look at the code seems to indicate
>> that this would only require a change in the header files.
>
> It would break every application looking at these datastructures
> right now.

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.