Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CrowdStrike Update: Windows Bluescreen and Boot Loops

old.reddit.com

Post reply on HN
Print view View original

221–230 of 1001 posts

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#221

Post by maeil »

novaRom wrote: post #136

Chances if Microsoft or Crowdstrike will be held liable for financial losses caused by this outage?

Financial losses? The comment you're replying to is mentioning heart attack treatment here. We're talking about deaths. Most of us won't like to hear this but for all of us who work at SaaS that is deployed on servers around the worlds, our bugs cause people to die. It's a given that at least a dozen people will die directly (medical flights, hospitals both being hit) due to this broken update, let alone indirectly.

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#228

Post by happyweasel »

techbrovanguard wrote: post #143

i've seen photos of the bsod from an affected machine, the error code is `PAGE_FAULT_IN_NONPAGED_AREA`. here's some helpful takeaways from this incident: 1) mistakes in kernel-level drivers can and will crash the entire os 2) do not write kernel-level drivers 3) do not write kernel-level drivers 4) do not write kernel-level drivers 5) if you really need a kernel-level driver, do not write it in a memory unsafe langua…

5) Well how much of those kernel-level drivers we rely upon ARE written in a memory unsafe language ??? Like 99% ?

And we are not crashing and dying every day?

Sure, Rust is the way to go. it just took Rust 18 years to mature to that level.

Also, quite frankly, if your unwrap() makes your program terminate because an array out of bounds isn't that exactly the same thing ? (program terminates)

But IMHO if we are hopping along a minefield at this moment every second of every day, well... If this is the worst case scenario, yeah it's not that worse after all.

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#229

Post by ndsipa_pomu »

pulkitsh1234 wrote: post #209

Workaround steps: https://www.reddit.com/r/crowdstrike/comments/1e6vmkf/commen...

> CrowdStrike Engineering has identified a content deployment related to this issue and reverted those changes.

> Workaround Steps:

> Boot Windows into Safe Mode or the Windows Recovery Environment

> Navigate to the C:\Windows\System32\drivers\CrowdStrike directory

> Locate the file matching “C-00000291*.sys”, and delete it.

> Boot the host normally.

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#230

Post by maeil »

techbrovanguard wrote: post #143

i've seen photos of the bsod from an affected machine, the error code is `PAGE_FAULT_IN_NONPAGED_AREA`. here's some helpful takeaways from this incident: 1) mistakes in kernel-level drivers can and will crash the entire os 2) do not write kernel-level drivers 3) do not write kernel-level drivers 4) do not write kernel-level drivers 5) if you really need a kernel-level driver, do not write it in a memory unsafe langua…

I've said this elsewhere but the enabling of instant auto-updates on software relied on by a mission critical system is a much bigger problem than kernel drivers.

Just imagine that there's a proprietary firewall that everyone uses on their production servers. No kernel-level drivers necessary. A broken update causes the firewall to blindly reject any kind of incoming or outgoing request.

Easier to rollback because the system didn't break? Not really, you can't even get into the system anymore without physical access. The chaos would be just as bad.

A firewall is an easy example, but it can be any kind of application. A broken update can effectively bring the system down.

Post reply on HN