[lkml]   [2017]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/7] signal/mips: Document a conflict with SI_USER with SIGFPE
On Mon, Aug 7, 2017 at 9:18 AM, Maciej W. Rozycki <> wrote:
> So what would be the right value of `si_code' to use here for such an
> unexpected exception condition? I think `BUG()' would be too big a
> hammer here. Or wouldn't it?

Hell no. NEVER EVER BUG().

The only case to use BUG() is if there is some core data structure
(say, kernel stack) that is so corrupted that you know you cannot
continue. That's the *only* valid use.

If this is a "this condition cannot happen" issue, then just remove
the damn conditional. It's pointless. Adding a BUG() to show "this
cannot happen" is not acceptable.


 \ /
  Last update: 2017-08-07 19:43    [W:0.103 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site