linux-kernel - Re: [PATCH] more helpful WARN_ON and BUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061020220717.GY3502@stusta.de>
Date:	Sat, 21 Oct 2006 00:07:17 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] more helpful WARN_ON and BUG_ON messages

On Fri, Oct 20, 2006 at 04:56:37PM -0500, Eric Sandeen wrote:
> Adrian Bunk wrote:
> 
> > Who really needs this considering it implies a size increase of the 
> > kernel image?
> > 
> > Using a kernel tree so unusual that you can't locate the source anymore 
> > sounds like an extremely rare and unintelligent situation, not something 
> > that must be handled.
> 
> Most debugging code makes the kernel bigger, slower... and easier to
> debug, no?
> 
> It's not a question of not being -able- to locate sources; it's a
> question of being able to look at a bug report and triage it quickly
> without digging around to find the kernel du jour that produced it.  *shrug*

It's not that BUGs were that frequent.

And with your suggestion "I suppose this could be put under CONFIG_DEBUG", 
it would anyway be turned off by nearly everyone.

> -Eric

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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