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... -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
