From: Peter Zijlstra <peterz@infradead.org>
To: Khalid Ali <khaliidcaliy@gmail.com>
Cc: dave.hansen@linux.intel.com, luto@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Fix log overwrite in CPA check_conflict()
Date: Fri, 20 Jun 2025 11:01:40 +0200 [thread overview]
Message-ID: <20250620090140.GR1613376@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250619174305.897-1-khaliidcaliy@gmail.com>
On Thu, Jun 19, 2025 at 05:42:41PM +0000, Khalid Ali wrote:
> From: Khalid Ali <khaliidcaliy@gmail.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
That's not good. Your system is sick, limiting the warns isn't making
that better.
next prev parent reply other threads:[~2025-06-20 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 17:42 Khalid Ali
2025-06-20 9:01 ` Peter Zijlstra [this message]
2025-06-20 18:20 ` Khalid Ali
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=20250620090140.GR1613376@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=khaliidcaliy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®