[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191024022307.GC11485@infradead.org>
Date: Wed, 23 Oct 2019 19:23:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Michal Suchanek <msuchanek@...e.de>
Cc: linux-scsi@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Jens Axboe <axboe@...nel.dk>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Eric Biggers <ebiggers@...gle.com>,
"J. Bruce Fields" <bfields@...hat.com>,
Benjamin Coddington <bcodding@...hat.com>,
Hannes Reinecke <hare@...e.com>,
Omar Sandoval <osandov@...com>, Ming Lei <ming.lei@...hat.com>,
Damien Le Moal <damien.lemoal@....com>,
Bart Van Assche <bvanassche@....org>,
Tejun Heo <tj@...nel.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 7/8] scsi: sr: workaround VMware ESXi cdrom emulation
bug
On Wed, Oct 23, 2019 at 02:52:46PM +0200, Michal Suchanek wrote:
>
> The drive claims to have a tray and claims to be able to close it.
> However, the UI has no notion of a tray - when medium is ejected it is
> dropped in the floor and the user must select a medium again before the
> drive can be re-loaded. On the kernel side the tray_move call to close
> the tray succeeds but the drive state does not change as a result of the
> call.
>
> The drive does not in fact emulate the tray state. There are two ways to
> get the medium state. One is the SCSI status:
Given that this is a buggy software emulation we should not add more
than 100 lines of kernel code to work around it. Ask VMware to fix
their mess instead.
Powered by blists - more mailing lists