Hector Martin

big oof

Seriously, "history file corrupt" is a common zsh complaint for me after a hard shutdown (on several systems) and then I have to open it in vim and nuke the last line full of ^@.

I've seen it with text syslogs too. And of course when it happens to systemd-jourmald binary logs it just craps itself hard and refuses to load them.

Ah, here we go, some discussion about this with @tytso. data=ordered only guarantees you won't get *garbage* (e.g. leaked free disk blocks, which is a huge security issue), but you can still get zeroes. https://plus.google.com/+KentonVarda/posts/JDwHfAiLGNQ …

i told you about how macOS's hardware video decode driver used to allocate vmem for frames without zeroing it, right?

I'd say "nice", but really, this is the kind of crap I expect in, like, every proprietary GPU driver for everything. Performance!!!!!ʷʰᵃᵗ ᶦˢ ᵗʰᵃᵗ ˢᵉᶜᵘʳᶦᵗʸ ᵗʰᶦⁿᵍ ʸᵒᵘ ˢᵃʸ?

i mean, when i reported it they fixed it pretty quickly, i think they just didn't realize that the decoder might not fill in the entire image you could get that to happen with some corrupted streams, but my favorite trick was just having the stream res < the container res

I once did, in fact, trace down cross-security domain unwritten sector leakage (that actually made it through *without* deliberate malicious recovery efforts and broke things) at a certain WebCo that liked to turn off ext3 journaling. My final diagnosis was working as designed...