From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Xu <peterx@redhat.com>, linux-kernel@vger.kernel.org
Cc: peterx@redhat.com, Ming Lei <ming.lei@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [PATCH] sched/isolation: Allow "isolcpus=" to skip unknown sub-parameters
Date: Wed, 01 Apr 2020 22:30:08 +0200 [thread overview]
Message-ID: <87d08rosof.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200204161639.267026-1-peterx@redhat.com>
Peter Xu <peterx@redhat.com> writes:
> @@ -169,8 +169,12 @@ static int __init housekeeping_isolcpus_setup(char *str)
> continue;
> }
>
> - pr_warn("isolcpus: Error, unknown flag\n");
> - return 0;
> + str = strchr(str, ',');
> + if (str)
> + /* Skip unknown sub-parameter */
> + str++;
> + else
> + return 0;
Just looked at it again because I wanted to apply this and contrary to
last time I figured out that this is broken:
isolcpus=nohz,domain1,3,5
is a malformatted option, but the above will make it "valid" and result
in:
HK_FLAG_TICK and a cpumask of 3,5.
The flags are required to be is_alpha() only. So you want something like
the untested below. Hmm?
Thanks,
tglx
8<---------------
--- a/kernel/sched/isolation.c
+++ b/kernel/sched/isolation.c
@@ -149,6 +149,8 @@ static int __init housekeeping_nohz_full
static int __init housekeeping_isolcpus_setup(char *str)
{
unsigned int flags = 0;
+ char *par;
+ int len;
while (isalpha(*str)) {
if (!strncmp(str, "nohz,", 5)) {
@@ -169,8 +171,17 @@ static int __init housekeeping_isolcpus_
continue;
}
- pr_warn("isolcpus: Error, unknown flag\n");
- return 0;
+ /*
+ * Skip unknown sub-parameter and validate that it is not
+ * containing an invalid character.
+ */
+ for (par = str, len = 0; isalpha(*str); str++, len++);
+ if (*str != ',') {
+ pr_warn("isolcpus: Invalid flag %*s\n", len, par);
+ return 0;
+ }
+ pr_info("isolcpus: Skipped unknown flag %*s\n", len, par);
+ str++;
}
/* Default behaviour for isolcpus without flags */
next prev parent reply other threads:[~2020-04-01 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 16:16 [PATCH] sched/isolation: Allow "isolcpus=" to skip unknown sub-parameters Peter Xu
2020-02-05 12:27 ` Ming Lei
2020-02-05 13:34 ` Peter Xu
2020-02-14 19:40 ` Peter Xu
2020-02-14 20:28 ` Thomas Gleixner
2020-03-09 15:19 ` Peter Xu
2020-03-31 20:57 ` Peter Xu
2020-04-01 20:30 ` Thomas Gleixner [this message]
2020-04-01 23:01 ` Peter Xu
2020-04-01 23:29 ` Thomas Gleixner
2020-04-02 0:50 ` Peter Xu
2020-04-02 8:40 ` Thomas Gleixner
2020-04-02 13:14 ` Peter Xu
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=87d08rosof.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mingo@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.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