linux-kernel - Re: [PATCH v2] driver core: Make cycle dev_info() message dev

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: <YLoj/2XmCo9OWjTS@kroah.com>
Date:   Fri, 4 Jun 2021 15:00:47 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     linux-kernel@...r.kernel.org,
        Saravana Kannan <saravanak@...gle.com>
Subject: Re: [PATCH v2] driver core: Make cycle dev_info() message dev_dbg()

On Thu, Jun 03, 2021 at 01:21:16PM -0700, Stephen Boyd wrote:
> This seems to mostly print debug information about device link stuff at
> boot. It doesn't seem very useful outside of debugging so move it to
> dev_dbg().

What messages at boot time are you seeing with this that should not be
there?  Shouldn't we fix the root cause here and not paper over it by
just lowering the logging level?

What drivers are having problems to trigger this?

thanks,

greg k-h