From nobody Mon Feb 9 16:53:59 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1675182787; cv=none; d=zohomail.com; s=zohoarc; b=nsv6e5xmK5ZO1qDikem/i7Oc/XuiVzZWMmCVSEwJlf0xxukyeH27hExKGGNON/9zeSTGwxxo0V2xmiM6Ibj3d3MjLvHNGPGtoEmEkc2t/x5qQodvLmPga1S0VIiXjwLK94lD31PxJCL5aTq7rbqP2KgCaIYnrpWYZbtPpcp3zng= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1675182787; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=BRt121TIKVCKR8pWZC+5bN9pSDrf8MA0U2SNeMfnbtc=; b=ZfA4QQDtDrnIqtMLNGRTYnlJwRdBXT1lradT6Prf0+vaYeHY+pWO74/q3l5VaEM7gz6ffNXbm1aer/DDNnVc7f8b5puTtZgz3Oo8ZBd727LL/TTBCKQ/MdyhS56NodBJbkzUj4fWtzcQCsLIU+ybOHWjUaKnuYqlHV+xwgrDr4w= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 1675182787854618.2477119501535; Tue, 31 Jan 2023 08:33:07 -0800 (PST) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-259-ekVSuy1QN-CHXXrRAfCLmA-1; Tue, 31 Jan 2023 11:32:49 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D35D53C41A0E; Tue, 31 Jan 2023 16:32:21 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0055140EBF4; Tue, 31 Jan 2023 16:32:21 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 9FB9B1946589; Tue, 31 Jan 2023 16:32:21 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id E85FF1946587 for ; Tue, 31 Jan 2023 16:32:20 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id DC354175A2; Tue, 31 Jan 2023 16:32:20 +0000 (UTC) Received: from speedmetal.lan (ovpn-208-29.brq.redhat.com [10.40.208.29]) by smtp.corp.redhat.com (Postfix) with ESMTP id DB1E5422F2 for ; Tue, 31 Jan 2023 16:32:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675182786; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=BRt121TIKVCKR8pWZC+5bN9pSDrf8MA0U2SNeMfnbtc=; b=Obv+U+HGO3crE5MXtABRyiCFp2+lPxCDWwcGX/sdFLSEpcq/qiJb8X+TwV0Ak1yLy65wGp h9dnfhFBCita2qnSMHNK1d9wgxq0W4Hzz1UlUVuZV0H6BA8icAwXh8vOV+Bxafnvx9SGC3 nivbUmgFIEgbE2vzTR3uPRaBKRqIYNA= X-MC-Unique: ekVSuy1QN-CHXXrRAfCLmA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 4/7] qemuFDPassTransferCommand: Mark that FD was passed Date: Tue, 31 Jan 2023 17:32:10 +0100 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1675182788278100001 Content-Type: text/plain; charset="utf-8" Until now the code didn't expect that we'd want to rollback/detach a FD passed on the commandline, but whith disk backend FD passing this can happen. Properly mark the 'qemuFDPass' object as passed to qemu even when it was done on the commandline. Signed-off-by: Peter Krempa --- src/qemu/qemu_fd.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/qemu/qemu_fd.c b/src/qemu/qemu_fd.c index 51a8133fde..ebeeb65505 100644 --- a/src/qemu/qemu_fd.c +++ b/src/qemu/qemu_fd.c @@ -151,6 +151,8 @@ qemuFDPassTransferCommand(qemuFDPass *fdpass, fdpass->fds[i].fd =3D -1; virCommandAddArgList(cmd, "-add-fd", arg, NULL); } + + fdpass->passed =3D true; } --=20 2.39.1