| 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
| ||
|
Date: Tue, 8 Oct 2013 18:41:08 +0200 From: Andi Kleen <andi@...stfloor.org> To: Steve Rago <sar@...-labs.com> Cc: Andy Lutomirski <luto@...capital.net>, Andi Kleen <andi@...stfloor.org>, David Miller <davem@...emloft.net>, Network Development <netdev@...r.kernel.org>, Michael Kerrisk-manpages <mtk.manpages@...il.com>, "Eric W. Biederman" <ebiederm@...ssion.com> Subject: Re: bug in passing file descriptors > I just want the semantics to be consistent. If you want Linux to > always require applications that call recvmsg to provide a buffer > size of CMSG_SPACE bytes long to retrieve control information, then > fail the system call when the buffer is smaller. But if you do > this, you risk breaking applications that work with FreeBSD, Mac OS > X, Solaris, and probably a few others. The primary concern is to be binary compatible with Linux. But not being compatible between 32bit and 64bit Linux processes on the same host would seem like a serious problem to me. > Regardless, copying 20 bytes and telling me you copied 24 is misleading and wrong. The question is could it break existing Linux applications to change it? And would it help with the 32/64bit compatibility? If not some other way to fix the compat layer would need to be found. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists