From: Ingo Molnar <mingo@kernel.org>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: peterz@infradead.org, mka@chromium.org, longman@redhat.com,
adobriyan@gmail.com, tglx@linutronix.de,
akpm@linux-foundation.org, tj@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix isocpus's param handling when CPUMASK_OFFSTACK=n.
Date: Fri, 20 Oct 2017 10:49:39 +0200 [thread overview]
Message-ID: <20171020084939.r6ox4o7k2kgezzbk@gmail.com> (raw)
In-Reply-To: <20171015131820.7173-1-rakib.mullick@gmail.com>
* Rakib Mullick <rakib.mullick@gmail.com> wrote:
> cpulist_parse() uses nr_cpumask_bits as limit to parse the
> passed buffer from kernel commandline. What nr_cpumask_bits
> represents varies depends upon CONFIG_CPUMASK_OFFSTACK option.
> If CONFIG_CPUMASK_OFFSTACK=n, then nr_cpumask_bits is same as
> NR_CPUS, which might not represent the # of cpus really exist
> (default 64). So, there's a chance of gap between nr_cpu_ids
> and NR_CPUS, which ultimately lead towards invalid cpulist_parse()
> operation. For example, if isolcpus=9 is passed on a 8 cpu
> system (CONFIG_CPUMASK_OFFSTACK=n) it doesn't show the error
> that it suppose to.
>
> This patch fixes this issue by effectively find out the last
> cpu of the passed isolcpus list and checking it with nr_cpu_ids.
> Also, fixes the error message where the nr_cpu_ids should be
> nr_cpu_ids-1, since the cpu numbering starts from 0.
>
> Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
> ---
> include/linux/cpumask.h | 16 ++++++++++++++++
> kernel/sched/topology.c | 8 +++++---
> 2 files changed, 21 insertions(+), 3 deletions(-)
What kernel is this against? It does not apply to the latest kernels.
Thanks,
Ingo
next prev parent reply other threads:[~2017-10-20 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 13:18 Rakib Mullick
2017-10-20 8:49 ` Ingo Molnar [this message]
2017-10-21 7:10 ` Rakib Mullick
2017-10-23 11:50 ` Ingo Molnar
2017-10-23 13:01 ` Rakib Mullick
2017-10-24 10:17 ` [tip:sched/core] sched/isolcpus: Fix "isolcpus=" boot parameter handling when !CONFIG_CPUMASK_OFFSTACK tip-bot for Rakib Mullick
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=20171020084939.r6ox4o7k2kgezzbk@gmail.com \
--to=mingo@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mka@chromium.org \
--cc=peterz@infradead.org \
--cc=rakib.mullick@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@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
Powered by JetHome