From: Borislav Petkov <bp@alien8•de>
To: Andrew Jones <ajones@ventanamicro•com>
Cc: Jonas Bonn <jonas@southpole•se>,
linux-s390@vger•kernel.org,
Alexander Gordeev <agordeev@linux•ibm.com>,
Dave Hansen <dave.hansen@linux•intel.com>,
Vasily Gorbik <gor@linux•ibm.com>,
Yury Norov <yury.norov@gmail•com>,
Heiko Carstens <hca@linux•ibm.com>,
x86@kernel•org,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Stefan Kristiansson <stefan.kristiansson@saunalahti•fi>,
openrisc@lists•librecores.org, Ingo Molnar <mingo@redhat•com>,
Palmer Dabbelt <palmer@dabbelt•com>,
Paul Walmsley <paul.walmsley@sifive•com>,
Stafford Horne <shorne@gmail•com>,
linux-riscv <linux-riscv@lists•infradead.org>,
"open list:LINUX FOR POWERPC PA SEMI PWRFICIENT"
<linuxppc-dev@lists•ozlabs.org>,
Thomas Gleixner <tglx@linutronix•de>,
Albert Ou <aou@eecs•berkeley.edu>
Subject: Re: [PATCH v3 2/2] x86: Fix /proc/cpuinfo cpumask warning
Date: Mon, 31 Oct 2022 09:58:57 +0100 [thread overview]
Message-ID: <Y1+OUawGJDjh4DOJ@zn.tnic> (raw)
In-Reply-To: <20221031080604.6xei6c4e3ckhsvmy@kamzik>
On Mon, Oct 31, 2022 at 09:06:04AM +0100, Andrew Jones wrote:
> The valid cpumask range is [0, nr_cpu_ids) and cpumask_next() always
> returns a CPU ID greater than its input, which results in its input
> range being [-1, nr_cpu_ids - 1). Ensure showing CPU info avoids
> triggering error conditions in cpumask_next() by stopping its loop
What error conditions?
What would happen if @n is outside of the valid range?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-10-31 9:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 15:58 [PATCH v3 0/2] Fix /proc/cpuinfo cpumask warning Andrew Jones
2022-10-14 15:58 ` [PATCH v3 1/2] RISC-V: " Andrew Jones
2022-10-14 15:58 ` [PATCH v3 2/2] x86: " Andrew Jones
2022-10-28 7:48 ` Andrew Jones
2022-10-28 14:46 ` Yury Norov
2022-10-28 15:03 ` Borislav Petkov
2022-10-28 15:13 ` Yury Norov
2022-10-28 16:06 ` Borislav Petkov
2022-10-31 8:06 ` Andrew Jones
2022-10-31 8:58 ` Borislav Petkov [this message]
2022-10-31 10:03 ` Andrew Jones
2022-11-02 18:44 ` Borislav Petkov
2022-11-03 12:59 ` Andrew Jones
2022-11-03 15:02 ` Borislav Petkov
2022-11-03 15:34 ` Andrew Jones
2022-11-03 15:54 ` Borislav Petkov
2022-11-03 16:30 ` yury.norov
2022-11-03 16:49 ` Borislav Petkov
2022-11-03 17:31 ` Yury Norov
2022-11-03 23:22 ` Borislav Petkov
2022-10-15 18:08 ` [PATCH v3 0/2] " Yury Norov
2022-10-27 23:07 ` Palmer Dabbelt
2022-10-28 7:40 ` 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=Y1+OUawGJDjh4DOJ@zn.tnic \
--to=bp@alien8$(echo .)de \
--cc=agordeev@linux$(echo .)ibm.com \
--cc=ajones@ventanamicro$(echo .)com \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=jonas@southpole$(echo .)se \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@redhat$(echo .)com \
--cc=openrisc@lists$(echo .)librecores.org \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=shorne@gmail$(echo .)com \
--cc=stefan.kristiansson@saunalahti$(echo .)fi \
--cc=tglx@linutronix$(echo .)de \
--cc=x86@kernel$(echo .)org \
--cc=yury.norov@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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