linux-kernel - Re: Debugging activated during runtime

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0710281717290.30465@fbirervta.pbzchgretzou.qr>
Date:	Sun, 28 Oct 2007 17:18:45 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Roel Kluin <12o3l@...cali.nl>
cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Debugging activated during runtime

On Oct 28 2007 17:07, Roel Kluin wrote:
>Jan Engelhardt wrote:
>> On Oct 28 2007 16:15, Roel Kluin wrote:
>>> Wouldn't it be nice to be able to specify upon loading, or during runtime
>>> to modules whether debug messages should be printed?
>> 
>> modprobe ark3116 debug=1
>> 
>> Nothing new.
>
>Ok, thanks and sorry, I didn't know that.

Loading debug info at runtime is more complex, and I doubt it is worth
the time. If writing a module, carefully consider when to print what.
When pr_*() comes in, this might be a bit relaxed.

>>> - A module could be loaded after an unexpected conditions (e.g. after a BUG_ON).
>> 
>> After a BUG_ON, you are probably next to a panic.
>
>Not always, it appears.
>

But anything can happen. It might end in a panic. Or it might eat your data.
-
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/