From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 6/6] sd: add support for TCG OPAL self encrypting disks Date: Tue, 6 Jun 2017 11:58:02 +0200 Message-ID: <20170606095802.GA20590@lst.de> References: <20170604124225.27032-1-hch@lst.de> <20170604124225.27032-7-hch@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.211]:45354 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751329AbdFFJ6E (ORCPT ); Tue, 6 Jun 2017 05:58:04 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: "Martin K. Petersen" Cc: Christoph Hellwig , Tejun Heo , Scott Bauer , Jonathan Derrick , Rafael Antognolli , Robert Elliott , linux-ide@vger.kernel.org, linux-block@vger.kernel.org, linux-scsi@vger.kernel.org On Mon, Jun 05, 2017 at 08:48:00PM -0400, Martin K. Petersen wrote: > For WRITE SAME, scsi_report_opcode() is gated not only by > sdev->no_report_opcodes but by sdev->no_write_same. > > I'm concerned about firing off REPORT OPCODES to random devices without > a sufficiently good heuristic. Doesn't look like SAT has anything to > offer in this department, though. Maybe it's time to consider a > vendor-specific Linux VPD page... Eww. Given that as far as I can tell only ATA devices implement OPAL we could key it off that for now. But that's only going to defer the problem until support for other security protocols comes along for real SCSI devices. But as we already set no_report_opcodes for all usb-storage and quirked uas devices I think the worst offenders are already covered anyway.