I suspect that we could persuade those caches to flush to RAM, simply by exhausting the number of possible lines for that address - if the cache is set-associative. Of course modern processors have multiple levels of cache, so that makes it harder.
Hi AC,
This is sort of self-contradictory, so I don't really need to respond to it directly. I just want to point one thing out. I can't afford to work for any company as less than a C-level employee. It would be a salary cut from my current business.
Not to mention that I'd not like it.
An AC talking about balls. Pathetic.
Right. I didn't even bother responding to the taunts.
Coward really means coward. I am sorry for the folks who are afraid that their employer will take a dislike of what they post, but for them we have handles.
I can't say I'm happy about what's happened to Debian. Having Ubuntu as a commercial derivative really has been the kiss of death for it, not that there were not other problems. It strikes me that the kernel team has done better for its lack of a constitution and elections, and Linus' ability to tell someone to screw off. I even got to tell him to screw off when he was dumping on 'Tridge over Bitkeeper. Somehow, that stuff works.
IMO, don't create a happy inclusive project team full of respect for each other. Hand-pick the geniuses and let them fight. You get better code in the end.
This actually has something to do with why so many people hate Systemd. It turns out that Systemd is professional-quality work done by competent salaried engineers. Our problem with it is that we're used to beautiful code made by geniuses. Going all of the way back to DMR.
It really does look like Jomo did post this article, and it refers to another article of his.
What isn't to like about Ubuntu is that it's a commercial project with a significant unpaid staff. Once in a while I make a point of telling the unpaid staff that there really are better ways that they could be helping Free Software.
It's just that I object folks who would be good community contributors being lured into being unpaid employees instead.
Say how do feel about idiots working for corporations contractually enmeshed with the US military-industrial-surveillance complex. Why no spittle-laced hate for them?
The GNU Radio project was funded in part by a United States intelligence agency. They paid good money and the result is under GPL. What's not to like?
Keep all of the idiots that want to work for a millionare for nothing. Fire the others.
Anyone with sense has by now joined a non-profit project.
Compare-and-exchange and mfence would be doing cache flush all of the way to RAM and global cache line invalidation, wouldn't they? So, they can potentially be used to hammer too.
Multi-threaded programs really do need those cache flushes to implement their interprocessor communications, don't they? It seems to me that they would be the ones most likely to hit this problem.
It has yet to be established whether hammer techniques can result in a correct data+ECC pattern. If so, it should be possible to permute the memory in a way that defeats this, either on the memory module or the memory controller.
That would make a good research paper for someone.
Yes, you beat me to it. A correctly-configured ECC motherboard with real ECC memory would defeat this. Watch out for fake ECC memory that just simulates the correction bits.
Once memory starts being vulnerable to row interference, having a machine without ECC becomes much more dangerous, regardless of this exploit.
That is not what I said. I never claimed that rsyslogd cannot cause corruption. I just claimed that there are not-so-rare cases where rsyslogd and alternatives work, while systemd causes corruption.
If that's what you said I'm afraid it wasn't obvious to me. I took "Systemd causes log corruption where sane alternatives do not have such issues" at face value.
In addition, the corruption by rsyslogd is usually what you describe, namely things cut short. With the binary log-format from systemd, the damage is far more extensive, so, yes, rotating them is "right", but having binary logs is deeply wrong in the first place.
I don't know anything about journald's format, but if it suffers 'extensive' damage under challenging conditions that syslog handles fine then it's not an appropriate binary format for this job. That's not a fault of binary (which can be as robust as you want), that's a fault of the wrong kind of binary.
I make no defence of systemd, I only respond to implications that syslog doesn't have its own problems with lost and corrupt messages.
Personally, I would prefer an investigation into why logs are being corrupted like this and a willingness to take it seriously rather than a 'corruption happens, rotate' attitude, but I'm just funny like that.
Good engineering would be to do both, not assume it's to be one or the other. This thread seems to be derived from 'Lennart said if there's corruption we rotate', I didn't see anything factual about the frequency and circumstances of corruption compared between different logging systems. It is a fact in my experience that all systems experience it occasionally.
You may know better than I do about systemd, which I don't currently use.
For Linux systems where the power is cycled often without warning, I have to use other kinds of logging for some things because syslog is too unreliable.
Have you looked at the data Chrome sends around?
I have and I wasn't happy about it when using Chrome for something that should have remained private to the application's users.
I tried every combination of command-line options, including undocumented ones, to turn off reporting to Google, including the options that are for this purpose, and there was still a trickle of reporting things that I didn't want reported.
But that was a few years ago. Maybe Chrome is more privacy respecting now
I don't mind that it talks to Google by default, after all there are some good services if you like them, and phishing protection (for example) is a good thing.
But I was surprised and disappointed that using all the options to turn off reporting didn't turn it all off.
Love may laugh at locksmiths, but he has a profound respect for money bags. -- Sidney Paternoster, "The Folly of the Wise"