From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Vernon Yang <vernon2gm@gmail.com>,
Yury Norov <yury.norov@gmail.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
mpe@ellerman.id.au, tytso@mit.edu, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
james.smart@broadcom.com, dick.kennedy@broadcom.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
christophe.leroy@csgroup.eu, npiggin@gmail.com,
dmitry.osipenko@collabora.com, joel@jms.id.au,
nathanl@linux.ibm.com, gustavoars@kernel.org,
naveen.n.rao@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.2 09/30] cpumask: fix incorrect cpumask scanning result checks
Date: Sun, 19 Mar 2023 18:59:07 -0700 [thread overview]
Message-ID: <CAHk-=wgpK-Gm-nOybRKs1LTD5yb7rPHQ4+=PCDvq61mUpBskYw@mail.gmail.com> (raw)
In-Reply-To: <20230320005258.1428043-9-sashal@kernel.org>
On Sun, Mar 19, 2023 at 5:53 PM Sasha Levin <sashal@kernel.org> wrote:
>
> [ Upstream commit 8ca09d5fa3549d142c2080a72a4c70ce389163cd ]
These are technically real fixes, but they are really just "documented
behavior" fixes, and don't actually matter unless you also have
596ff4a09b89 ("cpumask: re-introduce constant-sized cpumask
optimizations"), which doesn't look like stable material.
And if somebody *does* decide to backport commit 596ff4a09b89, you
should then backport all of
6015b1aca1a2 sched_getaffinity: don't assume 'cpumask_size()' is
fully initialized
e7304080e0e5 cpumask: relax sanity checking constraints
63355b9884b3 cpumask: be more careful with 'cpumask_setall()'
8ca09d5fa354 cpumask: fix incorrect cpumask scanning result checks
but again, none of these matter as long as the constant-sized cpumask
optimized case doesn't exist.
(Technically, FORCE_NR_CPUS also does the constant-size optimizations
even before, but that will complain loudly if that constant size then
doesn't match nr_cpu_ids, so ..).
Linus
prev parent reply other threads:[~2023-03-20 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230320005258.1428043-1-sashal@kernel.org>
2023-03-20 0:52 ` Sasha Levin
2023-03-20 1:59 ` Linus Torvalds [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='CAHk-=wgpK-Gm-nOybRKs1LTD5yb7rPHQ4+=PCDvq61mUpBskYw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=dick.kennedy@broadcom.com \
--cc=dmitry.osipenko@collabora.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=gustavoars@kernel.org \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vernon2gm@gmail.com \
--cc=wireguard@lists.zx2c4.com \
--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;
as well as URLs for NNTP newsgroup(s).