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, 29 Aug 2017 11:16:49 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'Vallish Vaidyeshwara' <vallish@...zon.com>, David Miller <davem@...emloft.net> CC: "shuah@...nel.org" <shuah@...nel.org>, "richardcochran@...il.com" <richardcochran@...il.com>, "xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "eduval@...zon.com" <eduval@...zon.com>, "anchalag@...zon.com" <anchalag@...zon.com> Subject: RE: [PATCH v2 0/2] enable hires timer to timeout datagram socket From: Vallish Vaidyeshwara > Sent: 27 August 2017 21:47 ... > I respect the decision not to upstream this patch series, however I > wanted to provide additional details. Application wanting high > resolution events with real guarantees is not the case, but the case > here is regression in system call behavior: > > 1) Change in system call behavior: > strace from 4.4 test run of waiting for 180 seconds on datagram socket: > 10:25:48.239685 setsockopt(3, SOL_SOCKET, SO_RCVTIMEO, "\264\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0 > 10:25:48.239755 recvmsg(3, 0x7ffd0a3beec0, 0) = -1 EAGAIN (Resource temporarily unavailable) > 10:28:48.236989 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0 IMHO you should be complaining to the main kernel group who 'broke' the timer code, not the networking group. David
Powered by blists - more mailing lists