linux-kernel - Re: Excessive logging in thunderbolt driver

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, 6 Nov 2017 20:27:04 +0100
From:   Andreas Noever <andreas.noever@...il.com>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     Stephen Hemminger <stephen@...workplumber.org>,
        Michael Jamet <michael.jamet@...el.com>,
        Yehezkel Bernat <yehezkel.bernat@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Excessive logging in thunderbolt driver

On Wed, Nov 1, 2017 at 8:41 AM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:
> On Tue, Oct 31, 2017 at 10:45:46PM +0100, Stephen Hemminger wrote:
>> The thunderbolt driver needs to stop logging.
>> All these debug messages and the laptop is on battery with no devices connected.
>> (I did use a USB key, but that is not a thunderbolt device).
>>
>> IMHO a production driver should log nothing in normal operation.
>> If you insist, the one message when device is found on discovery/probe
>> is allowed at INFO level.
>>
>> All the rest should just go away, or be turned into pr_debug().
>
> I agree and it is on my todo list for this driver.

Logging all the details was quite useful in the beginning to make the
driver work on hardware that was not available to me. But now that
thinks are mostly working I agree that we should turn the logging way
down.