Messages in this thread | | | Date | Mon, 8 Jun 2015 13:29:17 +0200 | From | Ingo Molnar <> | Subject | Re: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON() |
| |
* Alexander Holler <holler@ahsoftware.de> wrote:
> > Also note that BUG_ON() will make data corruption _worse_ statistically. Why? > > Because most data corruptions are unlikely to be perfectly detected by a > > BUG_ON(), and the BUG_ON() delays the finding of the underlying bug, so the > > bug will hit more people before it's fixed for good. > > > > So even in the cases where you could argue that the system needs to stop, > > because we have evidence of data corruption, it's statistically the better > > approach to continue and get kernel log info back to developers. > > Risking more, maybe even worse problems like corrupting file systems or similiar > in order to have a slightly chance of save log info?
That's not what I said - please read my argument and argue with that if you want, not with some other straw-man argument...
Thanks,
Ingo
| |