lkml.org 
[lkml]   [2015]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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


\
 
 \ /
  Last update: 2015-06-08 13:41    [W:0.089 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site