All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu@kernel.org>
To: Michael Kelley <mhklinux@outlook.com>
Cc: Waiman Long <longman@redhat.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>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] Drivers: hv: Avoid infinite retry loop in init_vp_index()
Date: Sun, 13 Sep 2026 15:34:26 -0700	[thread overview]
Message-ID: <20260913223426.GB2219269@liuwe-devbox-debian-v2.local> (raw)
In-Reply-To: <SN6PR02MB41574F4E654477ADF0242F4AD4A92@SN6PR02MB4157.namprd02.prod.outlook.com>

On Mon, Aug 31, 2026 at 01:25:23AM +0000, Michael Kelley wrote:
> From: Waiman Long <longman@redhat.com> Sent: Sunday, August 30, 2026 4:41 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(). Also update
> > the early abort check to check for the absence of online housekeeping
> > CPUs instead of just the emptiness of the cpumask. As the outer for
> > loop will only be reached if the housekeeping cpumask has at least one
> > online CPU, 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>
> > ---
[...]
> 
> Looks good.
> 
> Reviewed-by: Michael Kelley <mhkelley@outlook.com>

Applied. Thank you both.

Wei

> 

      reply	other threads:[~2026-09-13 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 23:41 [PATCH v5] Drivers: hv: Avoid infinite retry loop in init_vp_index() Waiman Long
2026-08-31  1:25 ` Michael Kelley
2026-09-13 22:34   ` Wei Liu [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=20260913223426.GB2219269@liuwe-devbox-debian-v2.local \
    --to=wei.liu@kernel.org \
    --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=longman@redhat.com \
    --cc=mhklinux@outlook.com \
    --cc=ssengar@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.