From: Yury Norov <yury.norov@gmail.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lkp@lists.01.org, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org
Subject: Re: [oliver.sang@intel.com: [cpumask] b9a7ecc71f: WARNING:at_include/linux/cpumask.h:#__is_kernel_percpu_address]
Date: Tue, 11 Oct 2022 10:23:27 -0700 [thread overview]
Message-ID: <Y0Wmj+XnyD/c6XM3@yury-laptop> (raw)
In-Reply-To: <Y0Wk0WD6CL4aFEIi@yury-laptop>
On Tue, Oct 11, 2022 at 10:16:03AM -0700, Yury Norov wrote:
> > Hi Yury,
> >
> > I just wanted to report that the warning fires when doing
> > 'cat /proc/cpuinfo' on at least x86 and riscv. I don't think
> > those are false positives. I'm guessing a patch should be
> > something like the following diff. If you haven't already
> > addressed this and I'm not off in left field, then I guess
> > we should integrate it into your series.
> >
> > Thanks,
> > drew
>
> Hi Andrew,
>
> Can you please send it as a patch with a description?
Also, can you describe why we'd silence the warning this way?
If the cpu number greater than nr_cpu_ids comes from upper layer,
we quite probably should investigate what happens there...
Thanks,
Yury
next prev parent reply other threads:[~2022-10-11 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 1:49 [oliver.sang@intel.com: [cpumask] b9a7ecc71f: WARNING:at_include/linux/cpumask.h:#__is_kernel_percpu_address] Yury Norov
2022-10-01 16:20 ` Linus Torvalds
2022-10-01 17:16 ` Yury Norov
2022-10-11 17:09 ` Andrew Jones
2022-10-11 17:16 ` Yury Norov
2022-10-11 17:21 ` Andrew Jones
2022-10-11 17:23 ` Yury Norov [this message]
2022-10-11 18:04 ` 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=Y0Wmj+XnyD/c6XM3@yury-laptop \
--to=yury.norov@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).