4 ms·
The actual bug is not that they pushed out a data file with all nulls. It’s that their kernel module crashes when it reads this file. I’m not surprised that th
by chatmasta 2y ago
The actual bug is not that they pushed out a data file with all nulls. It’s that their kernel module crashes when it reads this file.
I’m not surprised that there is no test pipeline for new data files. Those aren’t even really “build artifacts.” The software assumes they’re just data.
But I am surprised that the kernel module was deployed with a bug that crashed on a data file with all nulls.
(In fact, it’s so surprising, that I wonder if there is a known failing test in the codebase that somebody marked “skip” and then someone else decided to prove a point…)
Btw: is that bug in the kernel module even fixed? Or did they just delete the data file filled with nulls?
- hansvm 2y ago> Btw: is that bug in the kernel module even fixed? Or did they just delete the data file filled with nulls? Is that a real question? They definitely didn't do anything more than delete the file, perhaps just rename it.
- chatmasta 2y agoYeah they have been very obfuscatory in calling this a “fix.” I watched the CEO on Cramer and he kind of danced around this point.
- SoftTalker 2y agoThe instructions that my employer emailed were: 1. Start Windows in Safe Mode or the Windows Recovery Environment (Windows 11 option). 2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory. 3. Locate the file matching C-00000291*.sys and delete it. 4. Restart your device normally.