21–30 of 264 posts
If true, this is pretty huge. As if the AWS "You blew through your budget" emails right around midnight of New Years were only an appetizer. Edit: AWS Spurious Budget Email Barrage: https://www.reddit.com/r/aws/comments/7ndvli/anybody_get_spu...
I missed what happened with AWS? Any details
No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
It sounds like Intel, Google and Amazon are hiding something. Wouldn't want customers thinking that cloud computing is fundamentally insecure now would we?
This will be merged for 4.16, when there is no 4.15 release yet. No idea what your cloud computing companies run but it's not 4.15-dirty, and backporting this monster is a great recipe for a nightly emergency when it goes OOPS.
edit: it isn't even merged yet.
No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
AWS had scheduled maintenance requiring reboot of all EC2 instances in December. Maybe this is somehow related.
No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
AWS had scheduled maintenance requiring reboot of all EC2 instances in December. Maybe this is somehow related.
Shouldn't cloud-grade computers be immune to rowhammer (or at least rowhammer should be much less efficient) as they typically use ECC RAM. Switching ECC RAM in a way that also modifies checksum in a deterministic way is (was?) not practical?
Earlier quoted context omitted.
It sounds like Intel, Google and Amazon are hiding something. Wouldn't want customers thinking that cloud computing is fundamentally insecure now would we?
Well Intel for one manufactures the insecure CPUs.. This will be merged for 4.16, when there is no 4.15 release yet. No idea what your cloud computing companies run but it's not 4.15-dirty, and backporting this monster is a great recipe for a nightly emergency when it goes OOPS. edit: it isn't even merged yet.
No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
It sounds like Intel, Google and Amazon are hiding something. Wouldn't want customers thinking that cloud computing is fundamentally insecure now would we?
No ones hiding anything, this patchset was developed in the open for many many months. The hysteria and intrigue in this random tumblr blog is completely superfluous. It's a hardware bug anyway. Here is a good hint to when something is not being embargoed: there is a paper and a public demonstration.
The patchset being developed in the open, and the rationale for the development being done in the way it is, are two very different things.