Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <6cc250180e2cea8726a08c35f1020b200cc2bd5e.camel@perches.com>
Subject: Re: [PATCH RFC] locking/lockdep: replace simple printk by pr_info
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
Date:   Mon, 12 Nov 2018 07:02:07 -0800
In-Reply-To: <1542027794-2255-1-git-send-email-clabbe@baylibre.com>
References: <1542027794-2255-1-git-send-email-clabbe@baylibre.com>
Content-Type: text/plain; charset="ISO-8859-1"
User-Agent: Evolution 3.30.1-1build1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.