Re: [patch] change WARN_ON back to "BUG: at ..."

On Sat, 23 Dec 2006, Ingo Molnar wrote:

>
> i can whip up a patch for any of these conversions, but i dont think we
> need this flux right now.
>

I agree, it's not needed right now.  But making BUG_ON panic seems to be a
good idea, but if you do make that change (and even if you don't), could
you please add the dump_stack into panic (like you have in -rt)?  Thanks!

-- Steve

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch] change WARN_ON back to "BUG: at ..."
    • From: Ingo Molnar <[email protected]>
  • Re: [patch] change WARN_ON back to "BUG: at ..."
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: [patch] change WARN_ON back to "BUG: at ..."
    • From: Ingo Molnar <[email protected]>
  • Re: [patch] change WARN_ON back to "BUG: at ..."
    • From: Andrew Morton <[email protected]>
  • Re: [patch] change WARN_ON back to "BUG: at ..."
    • From: Steven Rostedt <[email protected]>
  • Re: [patch] change WARN_ON back to "BUG: at ..."
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address
• Next by Date: Re: bcm43xx from 2.6.20-rc1-mm1 on HPC nx6325 (x86_64)
• Previous by thread: Re: [patch] change WARN_ON back to "BUG: at ..."
• Next by thread: Re: [patch] change WARN_ON back to "BUG: at ..."
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]