Re: [PATCH 1/3] scsi: Do not allow user space to change the SCSI device state into SDEV_BLOCK

To: Bart Van Assche <bvanassche@xxxxxxx>
Subject: Re: [PATCH 1/3] scsi: Do not allow user space to change the SCSI device state into SDEV_BLOCK
From: Christoph Hellwig <hch@xxxxxx>
Date: Sat, 8 Jun 2019 11:35:48 +0200
Cc: "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, "James E . J . Bottomley" <jejb@xxxxxxxxxxxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>, Ming Lei <ming.lei@xxxxxxxxxx>, Hannes Reinecke <hare@xxxxxxxx>, Johannes Thumshirn <jthumshirn@xxxxxxx>, Hannes Reinecke <hare@xxxxxxx>, James Smart <james.smart@xxxxxxxxxxxx>
In-reply-to: <20190605201435.233701-2-bvanassche@acm.org>
User-agent: Mutt/1.5.17 (2007-11-01)

Thanks.  As discusssed before there really shouldn't be any reason
for users to inject a blocked state:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH 0/3] Avoid that .queuecommand() gets called for a quiesced SCSI device
  - From: Bart Van Assche
- [PATCH 1/3] scsi: Do not allow user space to change the SCSI device state into SDEV_BLOCK
  - From: Bart Van Assche