Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Po-Wen Kao <powenkao@google.com>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER"
	<linux-scsi@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] scsi: ufs: core: Fix error handler encryption support
Date: Tue, 16 Dec 2025 09:57:56 -0800	[thread overview]
Message-ID: <e0b4cfd3-2773-4a07-a3ba-3dc600ca69ac@acm.org> (raw)
In-Reply-To: <aUE4Kf73OxxO7r-K@infradead.org>

On 12/16/25 2:44 AM, Christoph Hellwig wrote:
> On Mon, Dec 15, 2025 at 08:47:03AM -0800, Bart Van Assche wrote:
>> (a) There is code in the SCSI error handler that submits SCSI commands
>>      with a data buffer. Hence, disabling encryption if and only if the
>>      data buffer length is zero can't fix the reported problem. From
>>      scsi_eh_prep_cmnd() in drivers/scsi/scsi_error.c:
> 
> This still does not actually transfer data to the media, and thus
> is not affected by inline encryption.

Hi Christoph,

Agreed that neither REQUEST SENSE nor any of the other SCSI commands
submitted by the SCSI error handler access the storage medium. However,
even if Po-Wen's patch would be modified such that it checks the SCSI
CDB to verify whether or not the SCSI command accesses the medium, the
other concerns that I mentioned still apply. So if nobody objects I
propose to repost patch "[PATCH v2 1/1] scsi: core: Fix error handler
encryption support" with v2 bumped to v3.

Thanks,

Bart.

      reply	other threads:[~2025-12-16 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  2:52 [PATCH 1/1] scsi: ufs: core: Fix error handler encryption support Po-Wen Kao
2025-12-09 17:53 ` Bart Van Assche
2025-12-10  6:48 ` Christoph Hellwig
2025-12-10 17:44   ` Bart Van Assche
2025-12-15  5:58     ` Christoph Hellwig
2025-12-15 16:47       ` Bart Van Assche
2025-12-16 10:44         ` Christoph Hellwig
2025-12-16 17:57           ` Bart Van Assche [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e0b4cfd3-2773-4a07-a3ba-3dc600ca69ac@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=powenkao@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox