From: Joe Perches <joe@perches.com>
To: Corentin Labbe <clabbe@baylibre.com>,
mingo@redhat.com, peterz@infradead.org, will.deacon@arm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] locking/lockdep: replace simple printk by pr_info
Date: Mon, 12 Nov 2018 07:02:07 -0800 [thread overview]
Message-ID: <6cc250180e2cea8726a08c35f1020b200cc2bd5e.camel@perches.com> (raw)
In-Reply-To: <1542027794-2255-1-git-send-email-clabbe@baylibre.com>
On Mon, 2018-11-12 at 13:03 +0000, Corentin Labbe wrote:
> While working on detector of new warn/err/crit/... messages, I found that the
> following messages was printed with the warn loglevel:
> [ 0.001607] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
> [ 0.001625] ... MAX_LOCKDEP_SUBCLASSES: 8
> [ 0.001641] ... MAX_LOCK_DEPTH: 48
> [ 0.001658] ... MAX_LOCKDEP_KEYS: 8191
> [ 0.001673] ... CLASSHASH_SIZE: 4096
> [ 0.001689] ... MAX_LOCKDEP_ENTRIES: 32768
> [ 0.001704] ... MAX_LOCKDEP_CHAINS: 65536
> [ 0.001719] ... CHAINHASH_SIZE: 32768
> [ 0.001735] memory used by lock dependency info: 4623 kB
>
> While the cause is still unknown to me, converting printk to pr_info fixed the issue.
because in lib/Kconfig.debug
config MESSAGE_LOGLEVEL_DEFAULT
int "Default message log level (1-7)"
range 1 7
default "4"
help
Default log level for printk statements with no specified priority.
This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
that are auditing their logs closely may want to set it to a lower
priority.
prev parent reply other threads:[~2018-11-12 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 13:03 Corentin Labbe
2018-11-12 15:02 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6cc250180e2cea8726a08c35f1020b200cc2bd5e.camel@perches.com \
--to=joe@perches.com \
--cc=clabbe@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®