From: Martin Kletzander <nert.pinx@gmail.com>
To: Fenghua Yu <fenghua.yu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/resctrl: Avoid overflow in MB settings in bw_validate()
Date: Mon, 16 Sep 2024 15:06:52 +0200 [thread overview]
Message-ID: <ZugtbMDP0AiPVrmt@wheatley.k8r.cz> (raw)
In-Reply-To: <f828f3177982a9cfe803d2aa8eb7602b70fcba50.1726482307.git.nert.pinx@gmail.com>
On Mon, Sep 16, 2024 at 12:37:13PM +0200, Martin Kletzander wrote:
>When resctrl is mounted with the "mba_MBps" option the default (maximum)
>bandwidth is the maximum unsigned value for the type. However when
>using the same value that already exists in the schemata file it is then
>rounded up to the bandwidth granularity and overflows to a small number
>instead, making it difficult to reset memory bandwidth allocation value
>back to its default.
>
>Since the granularity and minimum bandwidth are not used when the
>software controller is used (resctrl is mounted with the "mba_MBps"),
>skip the rounding up as well and return early from bw_validate().
>
>Signed-off-by: Martin Kletzander <nert.pinx@gmail.com>
>---
> arch/x86/kernel/cpu/resctrl/ctrlmondata.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
>diff --git a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>index 50fa1fe9a073..7e6014176a29 100644
>--- a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>+++ b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>@@ -48,8 +48,11 @@ static bool bw_validate(char *buf, unsigned long *data, struct rdt_resource *r)
> return false;
> }
>
>- if ((bw < r->membw.min_bw || bw > r->default_ctrl) &&
>- !is_mba_sc(r)) {
>+ /* Nothing else to do if software controller is enabled */
>+ if (is_mba_sc(r))
>+ return true;
I'm so sorry, I sent an incomplete patch. This still needs to modify
the *data argument. I'll send a v2 shortly.
>+
>+ if (bw < r->membw.min_bw || bw > r->default_ctrl) {
> rdt_last_cmd_printf("MB value %ld out of range [%d,%d]\n", bw,
> r->membw.min_bw, r->default_ctrl);
> return false;
>--
>2.46.0
>
prev parent reply other threads:[~2024-09-16 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 10:37 Martin Kletzander
2024-09-16 13:06 ` Martin Kletzander [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=ZugtbMDP0AiPVrmt@wheatley.k8r.cz \
--to=nert.pinx@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.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®