mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: Junrui Luo <moonafterrain@outlook.com>
Cc: Shameer Kolothum <skolothumtho@nvidia.com>,
	Yishai Hadas <yishaih@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Shay Drory <shayd@nvidia.com>, Kevin Tian <kevin.tian@intel.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yuhao Jiang <danisjiang@gmail.com>,
	stable@vger.kernel.org, alex@shazbot.org
Subject: Re: [PATCH] vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc
Date: Fri, 5 Jun 2026 13:26:15 -0600	[thread overview]
Message-ID: <20260605132615.50a26aae@shazbot.org> (raw)
In-Reply-To: <SYBPR01MB7881290BBDE79B61AE6A017FAF122@SYBPR01MB7881.ausprd01.prod.outlook.com>

On Tue, 02 Jun 2026 16:58:48 +0800
Junrui Luo <moonafterrain@outlook.com> wrote:

> vfio_mig_get_next_state() walks vfio_from_fsm_table[] one step at a time,
> looping to skip optional states the device does not support until
> *next_fsm is supported. A blocked transition is encoded as
> VFIO_DEVICE_STATE_ERROR, which the trailing return reports as -EINVAL.
> 
> The skip loop does not account for the ERROR sentinel.
> state_flags_table[ERROR] is ~0U and vfio_from_fsm_table[ERROR][*] is
> ERROR, so once *next_fsm becomes ERROR the loop condition stays true and
> *next_fsm never changes. The blocked arcs STOP_COPY -> PRE_COPY and
> STOP_COPY -> PRE_COPY_P2P map to ERROR yet pass the support check on a
> precopy-capable device, causing the loop to spin forever while holding
> the driver state mutex. This can result in a soft lockup, and a panic
> with softlockup_panic set.
> 
> Terminate the skip loop on the ERROR sentinel so a blocked transition
> falls through to the existing return and reports -EINVAL.
> 
> Fixes: 4db52602a607 ("vfio: Extend the device migration protocol with PRE_COPY")
> Reported-by: Yuhao Jiang <danisjiang@gmail.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Junrui Luo <moonafterrain@outlook.com>
> ---
>  drivers/vfio/vfio_main.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> index 6222376ab6ab..5e0422014523 100644
> --- a/drivers/vfio/vfio_main.c
> +++ b/drivers/vfio/vfio_main.c
> @@ -858,7 +858,8 @@ int vfio_mig_get_next_state(struct vfio_device *device,
>  	 * logical state, as per the above comment.
>  	 */
>  	*next_fsm = vfio_from_fsm_table[cur_fsm][new_fsm];
> -	while ((state_flags_table[*next_fsm] & device->migration_flags) !=
> +	while (*next_fsm != VFIO_DEVICE_STATE_ERROR &&
> +	       (state_flags_table[*next_fsm] & device->migration_flags) !=
>  			state_flags_table[*next_fsm])
>  		*next_fsm = vfio_from_fsm_table[*next_fsm][new_fsm];
>  

Applied to vfio next branch for v7.2.  Thanks,

Alex

      parent reply	other threads:[~2026-06-05 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  8:58 Junrui Luo
2026-06-03  1:05 ` Jason Gunthorpe
2026-06-03  6:45 ` Tian, Kevin
2026-06-05 19:26 ` Alex Williamson [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=20260605132615.50a26aae@shazbot.org \
    --to=alex@shazbot.org \
    --cc=danisjiang@gmail.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moonafterrain@outlook.com \
    --cc=shayd@nvidia.com \
    --cc=skolothumtho@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=yishaih@nvidia.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

all inboxes | Powered by JetHome®