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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 9 Nov 2017 21:16:13 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Patrick McLean <chutzpah@...too.org>, Bruce Fields <bfields@...hat.com>, "Darrick J. Wong" <darrick.wong@...cle.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux NFS Mailing List <linux-nfs@...r.kernel.org>, stable <stable@...r.kernel.org>, Thorsten Leemhuis <regressions@...mhuis.info> Subject: Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11 On Thu, Nov 09, 2017 at 12:04:19PM -0800, Linus Torvalds wrote: > That case has probably not gotten a huge amount of testing. As Al > points out, it can cause absolutely horrendous cache access pattern > changes, but it might also be triggering some corruption in case > there's a problem with the plugin, or with some piece of kernel code > that gets confused by it. I suspect that it might be an effect of randomize shite done both to struct mount *AND* to struct vfsmount embedded into it. With pointers to embedded struct vfsmount kept around a lot, and container_of() used to get from them to corresponding struct mount. That smells like a combination of idiocy that might have never occured to the authors of said gcc plugin. On the other hand, triggered gcc bugs certainly do add randomness, so good luck explaining to the security community that it's not a good idea...
Powered by blists - more mailing lists