linux-kernel - [tip:x86/urgent] x86/apic: Prevent pointless warning messages

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: <tip-df610d678893c85b82d3a68eea0d87dd4e03e615@git.kernel.org>
Date:   Sat, 8 Oct 2016 03:24:39 -0700
From:   tip-bot for Thomas Gleixner <tipbot@...or.com>
To:     linux-tip-commits@...r.kernel.org
Cc:     hpa@...or.com, mingo@...nel.org, douly.fnst@...fujitsu.com,
        guz.fnst@...fujitsu.com, markus@...ppelsdorf.de,
        tglx@...utronix.de, linux-kernel@...r.kernel.org,
        gnomes@...rguk.ukuu.org.uk
Subject: [tip:x86/urgent] x86/apic: Prevent pointless warning messages

Commit-ID:  df610d678893c85b82d3a68eea0d87dd4e03e615
Gitweb:     http://git.kernel.org/tip/df610d678893c85b82d3a68eea0d87dd4e03e615
Author:     Thomas Gleixner <tglx@...utronix.de>
AuthorDate: Fri, 7 Oct 2016 15:55:13 +0200
Committer:  Thomas Gleixner <tglx@...utronix.de>
CommitDate: Sat, 8 Oct 2016 12:18:36 +0200

x86/apic: Prevent pointless warning messages

Markus reported that he sees new warnings:

  APIC: NR_CPUS/possible_cpus limit of 4 reached.  Processor 4/0x84 ignored.
  APIC: NR_CPUS/possible_cpus limit of 4 reached.  Processor 5/0x85 ignored.

This comes from the recent persistant cpuid - nodeid changes. The code
which emits the warning has been called prior to these changes only for
enabled processors. Now it's called for disabled processors as well to get
the possible cpu accounting correct. So if the kernel is compiled for the
number of actual available/enabled CPUs and the BIOS reports disabled CPUs
as well then the above warnings are printed.

That's a pointless exercise as it only makes sense if there are more CPUs
enabled than the kernel supports.

Nake the warning conditional on enabled processors so we are back to the
state before these changes.

Fixes: 8f54969dc8d6 ("x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping") 
Reported-and-tested-by: Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: Dou Liyang <douly.fnst@...fujitsu.com>
Cc: linux-acpi@...r.kernel.org
Cc: Gu Zheng <guz.fnst@...fujitsu.com>
Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1610071549330.19804@nanos
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>

---
 arch/x86/kernel/apic/apic.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index f266b8a..88c657b 100644
--- a/arch/x86/kernel/apic/apic.c
+++ b/arch/x86/kernel/apic/apic.c
@@ -2128,9 +2128,11 @@ int __generic_processor_info(int apicid, int version, bool enabled)
 	if (num_processors >= nr_cpu_ids) {
 		int thiscpu = max + disabled_cpus;
 
-		pr_warning(
-			"APIC: NR_CPUS/possible_cpus limit of %i reached."
-			"  Processor %d/0x%x ignored.\n", max, thiscpu, apicid);
+		if (enabled) {
+			pr_warning("APIC: NR_CPUS/possible_cpus limit of %i "
+				   "reached. Processor %d/0x%x ignored.\n",
+				   max, thiscpu, apicid);
+		}
 
 		disabled_cpus++;
 		return -EINVAL;