From: Khalid Ali <khaliidcaliy@gmail.com>
To: peterz@infradead.org
Cc: dave.hansen@linux.intel.com, luto@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.c,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Fix log overwrite in CPA check_conflict()
Date: Fri, 20 Jun 2025 18:20:58 +0000 [thread overview]
Message-ID: <20250620182659.603-1-khaliidcaliy@gmail.com> (raw)
In-Reply-To: <20250620090140.GR1613376@noisy.programming.kicks-ass.net>
> > 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.
There is nothing wrong. It is just misconfiguration, however i don't see why
it is neccessary this warning to spam the dmesg log. Maybe it is better idea
to limit printing warning instead of warning for every page in a section (i.e Rodata in my case)
would make sense. So by limiting logs in anyways is good.
There is also overhead by logging if that happens.
Thanks
Khalid Ali
prev parent reply other threads:[~2025-06-20 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 17:42 [PATCH] x86/mm: Fix log overwrite in CPA check_conflict() Khalid Ali
2025-06-20 9:01 ` Peter Zijlstra
2025-06-20 18:20 ` Khalid Ali [this message]
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=20250620182659.603-1-khaliidcaliy@gmail.com \
--to=khaliidcaliy@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.c \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).