|
|
Log in / Subscribe / Register

What to do in response to a kernel warning

What to do in response to a kernel warning

Posted Nov 19, 2021 2:51 UTC (Fri) by pbonzini (subscriber, #60935)
In reply to: What to do in response to a kernel warning by dambacher
Parent article: What to do in response to a kernel warning

KVM recently added KVM_BUG_ON, which makes all subsequent ioctls return with EIO.


to post comments

What to do in response to a kernel warning

Posted Dec 10, 2021 20:32 UTC (Fri) by Vipketsh (guest, #134480) [Link]

Translated: they are turning a "potential issue" into "definitely an issue". Depending on the situation that can be anything from great to down right bastard.

If you are some cloud provider with a large number of machines (google, facebook, etc.), you probably have a bunch of redundancy and load balancing in your setup: if one machine goes down for whatever reason, even if just because of a "potential issue", there are a bunch more available to take over and the load balancing makes sure it happens. Furthermore the cloud provider probably has engineers available to take a look at the issue in short order and return the machine to operation. In such a setting taking machines down due to "potential issue" is very well warranted.

On the other hand if you are using the machine in question as a primary work machine, the last thing you want is for a "potential issue" to take down your system and eat hours of work with it. In such a scenario chugging along for as long as possible is the desired mode of operation.

I think google & co. have enough expertise on hand to tweak defaults to whatever makes sense for them while individuals (using Linux as a primary work machine) very often do not. Thus the only same thing is to keep the defaults to what makes sense for individuals: keep going for as long as possible.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds