linux-kernel - Re: [PATCH] net: trivial MLX4

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: <ada8xbw1qxt.fsf@cisco.com>
Date:	Thu, 10 May 2007 11:20:14 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	"Satyam Sharma" <satyam.sharma@...il.com>
Cc:	"Paul Mundt" <lethal@...ux-sh.org>,
	"Roland Dreier" <rolandd@...co.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: trivial MLX4_DEBUG dependency fix.

 > IMHO default configs must be aimed at production usage scenarios, so
 > are better off without debugging enabled by default. Except if the
 > driver is really new / EXPERIMENTAL where the goal is to get it tested
 > out by all users asap (and no production systems would be using it
 > anyway).

I agree, but I would hope that MLX4_DEBUG *is* enabled in production.
It doesn't print anything or introduce any measurable overhead except
for slightly larger code size unless the debug level is explicitly
increased, so the only reason to turn it off is if a few bytes of code
makes a big difference to you (hence making it selectable only if
EMBEDDED is selected).
-
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/