From: Borislav Petkov <bp@alien8.de>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Yury Norov <yury.norov@gmail.com>
Subject: Re: [PATCH] x86: Fix /proc/cpuinfo cpumask warning
Date: Tue, 11 Oct 2022 20:01:03 +0200 [thread overview]
Message-ID: <Y0WvX9Mp0kuohNdq@zn.tnic> (raw)
In-Reply-To: <20221011175031.1782748-1-ajones@ventanamicro.com>
On Tue, Oct 11, 2022 at 07:50:31PM +0200, Andrew Jones wrote:
> Upcoming cpumask changes will start issuing warnings[*] when cpu
What upcoming changes?
This needs a concrete pointer to a commit or so.
> indices equal to nr_cpu_ids are passed to cpumask_next* functions.
How do those indices get passed here? I think you need to explain how
exactly this happens.
> Ensure we don't generate a warning when reading /proc/cpuinfo by
Please use passive voice in your commit message: no "we" or "I", etc,
and describe your changes in imperative mood.
> validating the cpu index before calling cpumask_next().
s/cpu/CPU/g
> [*] Warnings will only appear with DEBUG_PER_CPU_MAPS enabled.
>
> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
> Cc: Yury Norov <yury.norov@gmail.com>
> ---
> arch/x86/kernel/cpu/proc.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/proc.c b/arch/x86/kernel/cpu/proc.c
> index 099b6f0d96bd..584ae6cb5b87 100644
> --- a/arch/x86/kernel/cpu/proc.c
> +++ b/arch/x86/kernel/cpu/proc.c
> @@ -153,9 +153,12 @@ static int show_cpuinfo(struct seq_file *m, void *v)
>
> static void *c_start(struct seq_file *m, loff_t *pos)
> {
> - *pos = cpumask_next(*pos - 1, cpu_online_mask);
> - if ((*pos) < nr_cpu_ids)
> - return &cpu_data(*pos);
> + if (*pos < nr_cpu_ids) {
> + *pos = cpumask_next(*pos - 1, cpu_online_mask);
> + if (*pos < nr_cpu_ids)
> + return &cpu_data(*pos);
> + }
Simpler: on function entry:
if (*pos >= nr_cpu_ids)
return NULL;
/* the rest remains unchanged */
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-10-11 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 17:50 Andrew Jones
2022-10-11 18:01 ` Borislav Petkov [this message]
2022-10-11 18:17 ` Andrew Jones
2022-10-11 19:02 ` Yury Norov
2022-10-12 6:51 ` Andrew Jones
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=Y0WvX9Mp0kuohNdq@zn.tnic \
--to=bp@alien8.de \
--cc=ajones@ventanamicro.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.com \
/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®