Context- someone on the birdside are blaming #crowdstrike on DEI hiring
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on 1/3
I saw an unsubstantiated claim this morning that the "channel file" to delete was full of NULs. If true, then the failure cannot even be down to a bad line of code, as it would also involve whatever tool generated the bad data file going very wrong.
However:
I am inclined to disbelieve this claim, as (for starters) this would result in a file without a valid PE header and a "channel file" is notionally an NT driver file as far as I can tell.
FWIW Crowdstrike posted an update that specifically refutes that hypothesis.
“This is not related to null bytes contained within Channel File 291 or any other Channel File.”
https://www.crowdstrike.com/blog/technical-details-on-todays-outage/
Yes. I caught up on that after I had caught up on the FediVerse posts.
I have a suspicion that the NULs thing is one of those Chinese Whispers distortions of someone talking about NULL pointers, in turn because they've just guessed that that was the STOP that occurred. (alas, see https://mastodonapp.uk/@JdeBP/112813708543808092, though)
I've certainly not seen an authoritative analysis of the specific crash that happens, yet, and certainly #CrowdStrike has not supplied one.
One interesting aspect of the #CrowdStrike saga is the #BadJournalism, where instead of actually getting a photographer out to one of the millions of PCs showing a BSOD today, some of which might even have been in the news organization's own offices, journalists have pulled up a stock BSOD image showing some random other error. I've seen critical thread/process terminations, unhandled exceptions, buffer overflows, and stack overruns so far. #NeverWindows11 #MO821132 #journalism @[email protected] @wood5y
Scott Hanselman 👸🏽🐝🌮
JdeBP
Covidiocracy