[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250619174305.897-1-khaliidcaliy@gmail.com>
Date: Thu, 19 Jun 2025 17:42:41 +0000
From: Khalid Ali <khaliidcaliy@...il.com>
To: dave.hansen@...ux.intel.com,
luto@...nel.org,
peterz@...radead.org,
tglx@...utronix.de,
mingo@...hat.com,
bp@...en8.de
Cc: x86@...nel.org,
hpa@...or.com,
linux-kernel@...r.kernel.org,
Khalid Ali <khaliidcaliy@...il.com>
Subject: [PATCH] x86/mm: Fix log overwrite in CPA check_conflict()
From: Khalid Ali <khaliidcaliy@...il.com>
On certain configurations (e.g. custom builds), check_conflict()
may produce a large number of warnings, flooding the kernel log
and overwriting earlier messages.
Observed warning:
CPA protect Rodata RO: 0xffff888022a75000 - 0xffff888022a75fff
PFN 22a75 req 8000000000000023 prevent 0000000000000002
Rate-limit these messages by replacing pr_warn() with
pr_warn_ratelimited().
Signed-off-by: Khalid Ali <khaliidcaliy@...il.com>
---
arch/x86/mm/pat/set_memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/mm/pat/set_memory.c b/arch/x86/mm/pat/set_memory.c
index 8834c76f91c9..bc5b62988b40 100644
--- a/arch/x86/mm/pat/set_memory.c
+++ b/arch/x86/mm/pat/set_memory.c
@@ -608,7 +608,7 @@ static inline void check_conflict(int warnlvl, pgprot_t prot, pgprotval_t val,
if (warnlvl > cpa_warn_level || !conflicts(prot, val))
return;
- pr_warn("CPA %8s %10s: 0x%016lx - 0x%016lx PFN %lx req %016llx prevent %016llx\n",
+ pr_warn_ratelimited("CPA %8s %10s: 0x%016lx - 0x%016lx PFN %lx req %016llx prevent %016llx\n",
lvltxt[warnlvl], txt, start, end, pfn, (unsigned long long)pgprot_val(prot),
(unsigned long long)val);
}
--
2.49.0
Powered by blists - more mailing lists