linux-kernel - Re: CONFIG_RTLWIFI

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]

Date:	Mon, 2 Apr 2012 22:53:22 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	"John W. Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Joe Perches <joe@...ches.com>
Subject: Re: CONFIG_RTLWIFI_DEBUG default y

On Mon, Apr 02, 2012 at 03:46:54PM -0500, Larry Finger wrote:
> Users will see nothing more than before!
> 
> Before CONFIG_RTLWIFI_DEBUG was allowed to be set, the driver always
> compiled in the debug code, but only those messages with the
> DBG_EMERG code were actually output. With the parameter set to Y,
> nothing changed. If the module is loaded with the "debug=X" option,
> where X is greater than 0, then other messages will be seen. That
> dynamic setting of the level is enough.
> 
> The only change when the configuration parameter is set to N is that
> the entire debug setup compiles away. The driver is a lot smaller,
> but there is no debugging.

Yes, yes, I knew there should be some sane default there,
rtlpriv->dbg.global_debuglevel remains 0 which is DBG_EMERG. I stand
corrected, thanks.

-- 
Regards/Gruss,
    Boris.
--
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/