From nobody Sun Dec 29 19:40:44 2024 Delivered-To: importer2@patchew.org Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer2=patchew.org@nongnu.org; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1720047098; cv=none; d=zohomail.com; s=zohoarc; b=PSdiaXUPSx78a68LHT0FGX6v6jrPUX3rCl5CYdQpg6AmxJm5+ujQuZAndnApW0p930T7l/ZF0OoqIFoaWziJh+ABqMoUP/EmEYQaym2DnDMs1V9mq4LyNW6ZEO301OnhnzdVflwub2i9hDm7kU0m0OuYFepTUMb+1bhh4g5hjNY= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1720047098; h=Content-Type:Cc:Cc:Date:Date:From:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:Subject:To:To:Message-Id:Reply-To; bh=/8Z7JyQo+HEEofucdvOkehCzjauROI/8uJ9hGYzaVe8=; b=SVXNF4MW3yWbKOqwr+95EQkzVAxUSooAWE2E2MgtTlUZVGlFxSKW5a0E6V2j7X9U2HxFrwqZtRn+THJWWRQZbqnT4hTVnaINzFN6BQ/8dw8fDSRI1EQlUD77oVB7pbtzr7vYnmoBwvZCcj2PynROQYK6y6wRFmBL+vfNeGlZCJE= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer2=patchew.org@nongnu.org; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1720047098382142.5005065665996; Wed, 3 Jul 2024 15:51:38 -0700 (PDT) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sP8mX-00027R-HX; Wed, 03 Jul 2024 18:48:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sP8mU-0001vW-Mp for qemu-devel@nongnu.org; Wed, 03 Jul 2024 18:48:54 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sP8mO-0005Er-P0 for qemu-devel@nongnu.org; Wed, 03 Jul 2024 18:48:54 -0400 Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-132-pR3UJFLcN7ehZCAdJQiAyQ-1; Wed, 03 Jul 2024 18:48:45 -0400 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-366e0a4c965so36907f8f.1 for ; Wed, 03 Jul 2024 15:48:45 -0700 (PDT) Received: from redhat.com ([2a0d:6fc7:441:91a8:a47d:5a9:c02f:92f2]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-36795e3fe31sm2235346f8f.21.2024.07.03.15.48.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 Jul 2024 15:48:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1720046927; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/8Z7JyQo+HEEofucdvOkehCzjauROI/8uJ9hGYzaVe8=; b=en8+Y/RtVJJ0ESaSUYFrpUgTIPJp1XPuuxi71mkEIoFDaaz/dRO03EnFPTzjoCaEdqavDp 6x3Yxw3P/q9U5vSWnLQXNBNiy1acqUp/woCHepCYlvZV6WNY19g8kz5OW6mFLr5EdYTV6l TFBFPhDYCOEvO4Hu/ked4vkJDu4xspU= X-MC-Unique: pR3UJFLcN7ehZCAdJQiAyQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720046924; x=1720651724; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=/8Z7JyQo+HEEofucdvOkehCzjauROI/8uJ9hGYzaVe8=; b=Nnw5Rh+Kzgb66wql9jthM/PUo6gcKvXSlE11TNdHjIf6YMT8E1tEDtaG4O+hHyriWJ NfKUcvFyP9LTmeFDp/PW8F0pUK1+iNrOegYmRz1QDq1ywwV5kbgJ0NSPjguc3f7EyjTs SYR9e+MIajFziAsoypGrQNh6eNFhvraa5Z9xaoRp7KfTisHMxGFJ8RyWzmCjZxhrGa6l cGfYikwaBUbP1CpNu58KVhiFtZZ3zv6xBZypTqb+UuiXIu2nvnIVdTmanJZjyZvSCJNJ Oes6g1urMStExhsP1VV7xKFBZw47CdXI2mxZ/Sg5rnytSSVYeIL2JEygmLX4GhOlIgvK aflQ== X-Gm-Message-State: AOJu0Yxdj9THjwDWOj00PTYTu6Y4tkotgl1SKRol7tNzgZR8pQz+idea kmov2egF0qFSdQdjzhSBVcPEJX0cTqwJ5905A7+H4cqsFNmXVk9OD3w/q+9yKDJ6Wrq7n0Q8BxM cTLVjaLSMzNrfKjcyMvk93mE2600YdTi9uLiAOuhY7/MPi58wBrR0KQCbO9lR0De6a7NL/MPmSk zTmamIAshga0QoMPXRtfNqm7BI8a+BTw== X-Received: by 2002:a05:6000:1c7:b0:367:9d7f:f83f with SMTP id ffacd0b85a97d-3679dd726b2mr1664f8f.58.1720046924304; Wed, 03 Jul 2024 15:48:44 -0700 (PDT) X-Google-Smtp-Source: AGHT+IF8qZJqSjyfGvwcojzk4qPbCDfOBYwefYkkeeU6ewQsN2S56NidapcoEG7//gi59wnWpnqbWA== X-Received: by 2002:a05:6000:1c7:b0:367:9d7f:f83f with SMTP id ffacd0b85a97d-3679dd726b2mr1654f8f.58.1720046923694; Wed, 03 Jul 2024 15:48:43 -0700 (PDT) Date: Wed, 3 Jul 2024 18:48:40 -0400 From: "Michael S. Tsirkin" To: qemu-devel@nongnu.org Cc: Peter Maydell , Thomas Huth , Manos Pitsidianakis Subject: [PULL v3 56/85] hw/virtio: Fix the de-initialization of vhost-user devices Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Mailer: git-send-email 2.27.0.106.g8ac3dc51b1 X-Mutt-Fcc: =sent Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer2=patchew.org@nongnu.org; helo=lists.gnu.org; Received-SPF: pass client-ip=170.10.133.124; envelope-from=mst@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+importer2=patchew.org@nongnu.org Sender: qemu-devel-bounces+importer2=patchew.org@nongnu.org X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1720047099139100003 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" From: Thomas Huth The unrealize functions of the various vhost-user devices are calling the corresponding vhost_*_set_status() functions with a status of 0 to shut down the device correctly. Now these vhost_*_set_status() functions all follow this scheme: bool should_start =3D virtio_device_should_start(vdev, status); if (vhost_dev_is_started(&vvc->vhost_dev) =3D=3D should_start) { return; } if (should_start) { /* ... do the initialization stuff ... */ } else { /* ... do the cleanup stuff ... */ } The problem here is virtio_device_should_start(vdev, 0) currently always returns "true" since it internally only looks at vdev->started instead of looking at the "status" parameter. Thus once the device got started once, virtio_device_should_start() always returns true and thus the vhost_*_set_status() functions return early, without ever doing any clean-up when being called with status =3D=3D 0. This causes e.g. problems when trying to hot-plug and hot-unplug a vhost user devices multiple times since the de-initialization step is completely skipped during the unplug operation. This bug has been introduced in commit 9f6bcfd99f ("hw/virtio: move vm_running check to virtio_device_started") which replaced should_start =3D status & VIRTIO_CONFIG_S_DRIVER_OK; with should_start =3D virtio_device_started(vdev, status); which later got replaced by virtio_device_should_start(). This blocked the possibility to set should_start to false in case the status flag VIRTIO_CONFIG_S_DRIVER_OK was not set. Fix it by adjusting the virtio_device_should_start() function to only consider the status flag instead of vdev->started. Since this function is only used in the various vhost_*_set_status() functions for exactly the same purpose, it should be fine to fix it in this central place there without any risk to change the behavior of other code. Fixes: 9f6bcfd99f ("hw/virtio: move vm_running check to virtio_device_start= ed") Buglink: https://issues.redhat.com/browse/RHEL-40708 Signed-off-by: Thomas Huth Message-Id: <20240618121958.88673-1-thuth@redhat.com> Reviewed-by: Manos Pitsidianakis Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin --- include/hw/virtio/virtio.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h index 1451926a13..7512afbc84 100644 --- a/include/hw/virtio/virtio.h +++ b/include/hw/virtio/virtio.h @@ -472,9 +472,9 @@ static inline bool virtio_device_started(VirtIODevice *= vdev, uint8_t status) * @vdev - the VirtIO device * @status - the devices status bits * - * This is similar to virtio_device_started() but also encapsulates a - * check on the VM status which would prevent a device starting - * anyway. + * This is similar to virtio_device_started() but ignores vdev->started + * and also encapsulates a check on the VM status which would prevent a + * device from starting anyway. */ static inline bool virtio_device_should_start(VirtIODevice *vdev, uint8_t = status) { @@ -482,7 +482,7 @@ static inline bool virtio_device_should_start(VirtIODev= ice *vdev, uint8_t status return false; } =20 - return virtio_device_started(vdev, status); + return status & VIRTIO_CONFIG_S_DRIVER_OK; } =20 static inline void virtio_set_started(VirtIODevice *vdev, bool started) --=20 MST