> > > The Intel people I asked last week weren't confident. For one thing, > > > I fully expect that rowhammer can be exploited using only reads and > > > writes with some clever tricks involving cache associativity. I don't > > > think there are any fully-associative caches, although the cache > > > replacement algorithm could make the attacks interesting. > > > > We should definitely get Intel/AMD to disable CLFLUSH, then. > > I doubt that would work, because you'd have to fix up all the faults from > userspace in things like graphics and video. Whether it is possible to > make the microcode do other accesses and delays I have no idea - but > that might also be quite horrible. > > A serious system should be using ECC memory anyway. and on things like > shared boxes it is probably not a root compromise that is the worst case > scenario but subtle undetected corruption of someone elses data > sets.
Both are bad. It is fairly hard to do rowhammer by accident, so if you are hitting it, someone is probably doing it on purpose. And cloud providers seem to be case of "serious systems" without ECC... (I seem to remember accidental rowhammer with spinlocks, will have to check that again). > That's what ECC already exists to protect against whether its from flawed > memory and rowhammer or just a vindictive passing cosmic ray. Well, there's more than thre orders of magnitude difference between cosmic rays and rowhammer. IIRC cosmic rays are expected to cause 2 bit flips a year... rowhammer can do bitflip in 10 minutes, and that is old version, not one of the optimized ones. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/