[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df42b70ed20d616d7c2d7f42cd38300115584619.1597677395.git.chris@chrisdown.name>
Date: Mon, 17 Aug 2020 16:24:36 +0100
From: Chris Down <chris@...isdown.name>
To: linux-kernel@...r.kernel.org
Cc: Borislav Petkov <bp@...e.de>, Jakub Kicinski <kuba@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>, kernel-team@...com,
sean.j.christopherson@...el.com, tony.luck@...el.com,
torvalds@...ux-foundation.org, x86@...nel.org
Subject: [PATCH 2/2] x86: Make source of unrecognised MSR writes unambiguous
In many cases the comm enough isn't enough to distinguish the offender,
since for interpreted languages it's likely just going to be "python3"
or whatever. Add the pid to make it unambiguous.
Signed-off-by: Chris Down <chris@...isdown.name>
Cc: Borislav Petkov <bp@...e.de>
Cc: Jakub Kicinski <kuba@...nel.org>
---
arch/x86/kernel/msr.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/msr.c b/arch/x86/kernel/msr.c
index 3babb0e58b0e..76b6b0011d62 100644
--- a/arch/x86/kernel/msr.c
+++ b/arch/x86/kernel/msr.c
@@ -99,8 +99,9 @@ static int filter_write(u32 reg)
if (!__ratelimit(&fw_rs) || reg == MSR_IA32_ENERGY_PERF_BIAS)
return 0;
- pr_err("Write to unrecognized MSR 0x%x by %s\n"
- "Please report to x86@...nel.org\n", reg, current->comm);
+ pr_err("Write to unrecognized MSR 0x%x by pid %s:%d\n"
+ "Please report to x86@...nel.org\n",
+ reg, current->comm, current->pid);
return 0;
}
--
2.28.0
Powered by blists - more mailing lists