From nobody Tue Nov 11 15:35:42 2025 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1564418616; cv=none; d=zoho.com; s=zohoarc; b=DPcPI3kCwfWrDOcNSBhR+YnbtrMh5rZXuoN/Os3pRgFSChnTIvHmtpTFm23KRlyhijOFCA21qFAarSa/RvzuVTOMqbT4/6MdqKN1WYu9RJ3oZd4BdI8dACPPVknArhqGa8oBb581o2ge/HkjCeZUmVyxh1am8spxV0MW9A7Ic2k= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com; s=zohoarc; t=1564418616; h=Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To:ARC-Authentication-Results; bh=11XhCHobE7fkdnt/07W7Siv3v1se1ES5z0NguRhqdL0=; b=RFpGnlmniIqBpXPV9nz9qj7ZoxYXl7djZWqFSk8v3vW5PyKJEyReSMSMw2/uYFLFu5j7wPRxduL5aXDVcpN0p6F3Pz4QoGlK7mvBiUtb0Hg7Lz8BL7Bw0VLcXSifym4QaPgFhNoZuc2S3C+garoA5iPndPndx3uPvvD580xQSO8= ARC-Authentication-Results: i=1; mx.zoho.com; spf=pass (zoho.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from lists.gnu.org (209.51.188.17 [209.51.188.17]) by mx.zohomail.com with SMTPS id 1564418616628247.8821130161523; Mon, 29 Jul 2019 09:43:36 -0700 (PDT) Received: from localhost ([::1]:55110 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs8kC-0005e3-7d for importer@patchew.org; Mon, 29 Jul 2019 12:43:28 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:33183) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs8jV-0005AF-6Y for qemu-devel@nongnu.org; Mon, 29 Jul 2019 12:42:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hs8jU-00074w-0N for qemu-devel@nongnu.org; Mon, 29 Jul 2019 12:42:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50790) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hs8jR-00073d-Mg; Mon, 29 Jul 2019 12:42:41 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1181B4A6FB; Mon, 29 Jul 2019 16:42:41 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-116-188.ams2.redhat.com [10.36.116.188]) by smtp.corp.redhat.com (Postfix) with ESMTP id BDF1D5C1A1; Mon, 29 Jul 2019 16:42:39 +0000 (UTC) From: Kevin Wolf To: qemu-block@nongnu.org Date: Mon, 29 Jul 2019 18:42:34 +0200 Message-Id: <20190729164234.11573-1-kwolf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 29 Jul 2019 16:42:41 +0000 (UTC) Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" Content-Type: text/plain; charset="utf-8" scsi-disks decides whether it has a read-only device by looking at whether the BlockBackend specified as drive=3D... is read-only. In the case of an anonymous BlockBackend (with a node name specified in drive=3D...), this is the read-only flag of the attached node. In the case of an empty anonymous BlockBackend, it's always read-write because nothing prevented it from being read-write. This is a problem because scsi-cd would take write permissions on the anonymous BlockBackend of an empty drive created without a drive=3D... option. Using blockdev-insert-medium with a read-only node fails then with the error message "Block node is read-only". Fix scsi_realize() so that scsi-cd devices always take read-only permissions on their BlockBackend instead. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=3D1733920 Signed-off-by: Kevin Wolf Reviewed-by: Markus Armbruster Reviewed-by: Max Reitz Reviewed-by: Philippe Mathieu-Daud=C3=A9 --- hw/scsi/scsi-disk.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c index 8e95e3e38d..af3e622dc5 100644 --- a/hw/scsi/scsi-disk.c +++ b/hw/scsi/scsi-disk.c @@ -2318,6 +2318,7 @@ static void scsi_disk_unit_attention_reported(SCSIDev= ice *dev) static void scsi_realize(SCSIDevice *dev, Error **errp) { SCSIDiskState *s =3D DO_UPCAST(SCSIDiskState, qdev, dev); + bool read_only; =20 if (!s->qdev.conf.blk) { error_setg(errp, "drive property not set"); @@ -2351,8 +2352,13 @@ static void scsi_realize(SCSIDevice *dev, Error **er= rp) return; } } - if (!blkconf_apply_backend_options(&dev->conf, - blk_is_read_only(s->qdev.conf.blk), + + read_only =3D blk_is_read_only(s->qdev.conf.blk); + if (dev->type =3D=3D TYPE_ROM) { + read_only =3D true; + } + + if (!blkconf_apply_backend_options(&dev->conf, read_only, dev->type =3D=3D TYPE_DISK, errp)) { return; } --=20 2.20.1