Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-30 Thread Markus Armbruster
Max Reitz writes: > On 30.07.19 10:29, Kevin Wolf wrote: >> Am 30.07.2019 um 08:31 hat Markus Armbruster geschrieben: >>> Kevin Wolf writes: >>> scsi-disks decides whether it has a read-only device by looking at whether the BlockBackend specified as drive=... is read-only. In the

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-30 Thread Max Reitz
On 29.07.19 18:42, Kevin Wolf wrote: > scsi-disks decides whether it has a read-only device by looking at > whether the BlockBackend specified as drive=... is read-only. In the > case of an anonymous BlockBackend (with a node name specified in > drive=...), this is the read-only flag of the attache

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-30 Thread Max Reitz
On 30.07.19 10:29, Kevin Wolf wrote: > Am 30.07.2019 um 08:31 hat Markus Armbruster geschrieben: >> Kevin Wolf writes: >> >>> scsi-disks decides whether it has a read-only device by looking at >>> whether the BlockBackend specified as drive=... is read-only. In the >>> case of an anonymous BlockBa

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-30 Thread Christophe de Dinechin
Kevin Wolf writes: > scsi-disks decides whether it has a read-only device by looking at > whether the BlockBackend specified as drive=... is read-only. In the > case of an anonymous BlockBackend (with a node name specified in > drive=...), this is the read-only flag of the attached node. In the

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-30 Thread Kevin Wolf
Am 30.07.2019 um 08:31 hat Markus Armbruster geschrieben: > Kevin Wolf writes: > > > scsi-disks decides whether it has a read-only device by looking at > > whether the BlockBackend specified as drive=... is read-only. In the > > case of an anonymous BlockBackend (with a node name specified in > >

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-29 Thread Markus Armbruster
Kevin Wolf writes: > scsi-disks decides whether it has a read-only device by looking at > whether the BlockBackend specified as drive=... is read-only. In the > case of an anonymous BlockBackend (with a node name specified in > drive=...), this is the read-only flag of the attached node. In the c

Re: [Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-29 Thread Philippe Mathieu-Daudé
On 7/29/19 6:42 PM, Kevin Wolf wrote: > scsi-disks decides whether it has a read-only device by looking at > whether the BlockBackend specified as drive=... is read-only. In the > case of an anonymous BlockBackend (with a node name specified in > drive=...), this is the read-only flag of the attach

[Qemu-devel] [PATCH for-4.1] scsi-cd: Fix inserting read-only media in empty drive

2019-07-29 Thread Kevin Wolf
scsi-disks decides whether it has a read-only device by looking at whether the BlockBackend specified as drive=... is read-only. In the case of an anonymous BlockBackend (with a node name specified in drive=...), this is the read-only flag of the attached node. In the case of an empty anonymous Blo