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
| ||
|
Message-Id: <20160809.120458.792987014914899369.davem@davemloft.net> Date: Tue, 09 Aug 2016 12:04:58 -0700 (PDT) From: David Miller <davem@...emloft.net> To: rapier@....edu Cc: netdev@...r.kernel.org Subject: Re: size of data_segs_[in|out] and segs_[in|out] 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. You need to find another solution to the problem, or advocate a user side solution (periodic polling).
Powered by blists - more mailing lists