From: Pablo Neira Ayuso <pablo@netfilter•org>
To: Julian Anastasov <ja@ssi•bg>
Cc: Waiman Long <longman@redhat•com>,
Simon Horman <horms@verge•net.au>,
"David S. Miller" <davem@davemloft•net>,
David Ahern <dsahern@kernel•org>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Florian Westphal <fw@strlen•de>, Phil Sutter <phil@nwl•cc>,
Frederic Weisbecker <frederic@kernel•org>,
Chen Ridong <chenridong@huawei•com>, Phil Auld <pauld@redhat•com>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
lvs-devel@vger•kernel.org, netfilter-devel@vger•kernel.org,
coreteam@netfilter•org, sheviks <sheviks@gmail•com>
Subject: Re: [PATCH-next v2 0/2] ipvs: Fix incorrect use of HK_TYPE_KTHREAD housekeeping cpumask
Date: Fri, 3 Apr 2026 16:29:05 +0200 [thread overview]
Message-ID: <ac_OscBPYRwt73ic@lemonverbena> (raw)
In-Reply-To: <cd9afe18-9862-6005-f7d9-d69425b7d4cf@ssi.bg>
On Fri, Apr 03, 2026 at 05:15:50PM +0300, Julian Anastasov wrote:
>
> Hello,
>
> On Tue, 31 Mar 2026, Waiman Long wrote:
>
> > v2:
> > - Rebased on top of linux-next
> >
> > Since commit 041ee6f3727a ("kthread: Rely on HK_TYPE_DOMAIN for preferred
> > affinity management"), the HK_TYPE_KTHREAD housekeeping cpumask may no
> > longer be correct in showing the actual CPU affinity of kthreads that
> > have no predefined CPU affinity. As the ipvs networking code is still
> > using HK_TYPE_KTHREAD, we need to make HK_TYPE_KTHREAD reflect the
> > reality.
> >
> > This patch series makes HK_TYPE_KTHREAD an alias of HK_TYPE_DOMAIN
> > and uses RCU to protect access to the HK_TYPE_KTHREAD housekeeping
> > cpumask.
> >
> > Waiman Long (2):
> > sched/isolation: Make HK_TYPE_KTHREAD an alias of HK_TYPE_DOMAIN
> > ipvs: Guard access of HK_TYPE_KTHREAD cpumask with RCU
>
> The patchset looks good to me for nf-next, thanks!
>
> Acked-by: Julian Anastasov <ja@ssi•bg>
>
> Pablo, Florian, as a bugfix this patchset missed
> the chance to be applied before the changes that are in
> nf-next in ip_vs.h, there is little fuzz there. If there
> is no chance to resolve it somehow, we can apply it
> on top of nf-next where it now applies successfully.
One way to handle this is to follow up with nf-next as you suggest,
then send a backport that applies cleanly for -stable once it is
released.
Else, let me know if I am misunderstanding.
next prev parent reply other threads:[~2026-04-03 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:50 [PATCH-next v2 0/2] ipvs: Fix incorrect use of HK_TYPE_KTHREAD housekeeping cpumask Waiman Long
2026-03-31 16:50 ` [PATCH-next v2 1/2] sched/isolation: Make HK_TYPE_KTHREAD an alias of HK_TYPE_DOMAIN Waiman Long
2026-04-01 12:43 ` Frederic Weisbecker
2026-03-31 16:50 ` [PATCH-next v2 2/2] ipvs: Guard access of HK_TYPE_KTHREAD cpumask with RCU Waiman Long
2026-04-01 12:54 ` Frederic Weisbecker
2026-04-01 15:13 ` Waiman Long
2026-04-03 14:15 ` [PATCH-next v2 0/2] ipvs: Fix incorrect use of HK_TYPE_KTHREAD housekeeping cpumask Julian Anastasov
2026-04-03 14:29 ` Pablo Neira Ayuso [this message]
2026-04-03 15:00 ` Julian Anastasov
2026-04-20 17:24 ` Julian Anastasov
2026-04-20 17:45 ` Pablo Neira Ayuso
2026-04-20 18:13 ` Julian Anastasov
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=ac_OscBPYRwt73ic@lemonverbena \
--to=pablo@netfilter$(echo .)org \
--cc=chenridong@huawei$(echo .)com \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=frederic@kernel$(echo .)org \
--cc=fw@strlen$(echo .)de \
--cc=horms@verge$(echo .)net.au \
--cc=ja@ssi$(echo .)bg \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=longman@redhat$(echo .)com \
--cc=lvs-devel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pauld@redhat$(echo .)com \
--cc=phil@nwl$(echo .)cc \
--cc=sheviks@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