From: Waiman Long <longman@redhat.com>
To: Michael Kelley <mhklinux@outlook.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Long Li <longli@microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Michael Kelley <mikelley@microsoft.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Drivers: hv: Avoid infinite retry loop in init_vp_index()
Date: Fri, 28 Aug 2026 21:21:35 -0400 [thread overview]
Message-ID: <aaf4826e-6b25-45ff-8aec-8cfeae3b4fd5@redhat.com> (raw)
In-Reply-To: <SN6PR02MB415755118796082D643126ACD4AD2@SN6PR02MB4157.namprd02.prod.outlook.com>
On 8/27/26 5:10 PM, Michael Kelley wrote:
> From: Waiman Long <longman@redhat.com> Sent: Thursday, August 27, 2026 12:38 PM
>> There is a retry loop in init_vp_index() where the CPUs from a certain
>> node are stripped out if they have already been in the allocated cpumask
>> or not in HK_TYPE_MANAGED_IRQ housekeeping cpumask. If there is no
>> CPU left, the allocated cpumask is ignored and the process is retried
>> again. However, if the HK_TYPE_MANAGED_IRQ housekeeping cpumask turns
>> out not to contain any CPU in that particular node, that will become an
>> infinite retry loop. This particular problem was reported by sashiko
>> [1]. This should rarely happen, but we still need to guard against this.
>>
>> Fix this infinite loop problem by also skipping NUMA node that has no
>> housekeeping CPU in the inner while loop of init_vp_index(). As the outer
>> for loop will only be reached if the housekeeping cpumask isn't empty,
>> a NUMA node with housekeeping CPUs will eventually be found.
>>
>> Link: https://sashiko.dev/#/message/20260422030903.E1BFCC2BCB0%40smtp.kernel.org [1]
>> Fixes: 6640b5df1a38 ("Drivers: hv: vmbus: Don't assign VMbus channel interrupts to isolated CPUs")
>> Signed-off-by: Waiman Long <longman@redhat.com>
>> ---
>> drivers/hv/channel_mgmt.c | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
>> index 89d214dda360..ed121d74d73f 100644
>> --- a/drivers/hv/channel_mgmt.c
>> +++ b/drivers/hv/channel_mgmt.c
>> @@ -752,6 +752,7 @@ static void init_vp_index(struct vmbus_channel *channel)
>> u32 i, ncpu = num_online_cpus();
>> cpumask_var_t available_mask;
>> struct cpumask *allocated_mask;
>> + const struct cpumask *node_mask;
>> const struct cpumask *hk_mask = housekeeping_cpumask(HK_TYPE_MANAGED_IRQ);
>> u32 target_cpu;
>> int numa_node;
>> @@ -780,14 +781,16 @@ static void init_vp_index(struct vmbus_channel *channel)
>> next_numa_node_id = 0;
>> continue;
>> }
>> - if (cpumask_empty(cpumask_of_node(numa_node)))
>> + node_mask = cpumask_of_node(numa_node);
>> + if (cpumask_empty(node_mask) ||
>> + !cpumask_intersects(node_mask, hk_mask))
> The cpumask_empty() test looks to be redundant. The
> cpumask_intersects() test will catch the case where
> node_mask is empty.
>
> Otherwise, I think this looks good as a solution to the core
> problem.
>
> Michael
Yes, I am aware that cpumask_empty() test is redundant and can be
skipped. I keep it just to make it easier to read. I can certainly drop
the cpumask_empty() statement.
Cheers,
Longman
>
>> continue;
>> break;
>> }
>> allocated_mask = &hv_context.hv_numa_map[numa_node];
>>
>> retry:
>> - cpumask_xor(available_mask, allocated_mask, cpumask_of_node(numa_node));
>> + cpumask_xor(available_mask, allocated_mask, node_mask);
>> cpumask_and(available_mask, available_mask, hk_mask);
>>
>> if (cpumask_empty(available_mask)) {
>> --
>> 2.55.0
>>
prev parent reply other threads:[~2026-08-29 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 19:37 Waiman Long
2026-08-27 21:10 ` Michael Kelley
2026-08-29 1:21 ` Waiman Long [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=aaf4826e-6b25-45ff-8aec-8cfeae3b4fd5@redhat.com \
--to=longman@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=mikelley@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@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
all inboxes | Powered by JetHome®