From: Nathan Chancellor <nathan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, stable@vger.kernel.org,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] arch_numa: Avoid false positive fortify warning in setup_node_to_cpumask_map()
Date: Wed, 12 Aug 2026 18:32:03 -0700 [thread overview]
Message-ID: <20260813013203.GA3920328@ax162> (raw)
In-Reply-To: <20260811224746.fdb85bcf47533e12d365b182@linux-foundation.org>
On Tue, Aug 11, 2026 at 10:47:46PM -0700, Andrew Morton wrote:
> (cc Kees)
Thanks, should have done that originally, I cc'd him on the original
issue.
> Sashiko wants a \n there.
Thanks, will send v2 with this tomorrow.
> Lord only knows why nr_node_ids is unsigned but MAX_NUMNODES is signed.
I can change the specifier for MAX_NUMNODES to unsigned as well (even if
it is technically signed due to the signed '1' literal in its
definition) since it should never be negative, up to you.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-08-13 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 5:22 [PATCH] arch_numa: Avoid false positive fortify warning in setup_node_to_cpumask_map() Nathan Chancellor
2026-08-12 5:47 ` Andrew Morton
2026-08-13 1:32 ` Nathan Chancellor [this message]
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=20260813013203.GA3920328@ax162 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=rppt@kernel.org \
--cc=stable@vger.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