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: Mon, 15 Dec 2025 08:47:03 -0800	[thread overview]
Message-ID: <54d824db-ec39-447c-8eab-6c2ce4ca87a6@acm.org> (raw)
In-Reply-To: <aT-jjQpp1UfaiZIU@infradead.org>

On 12/14/25 9:58 PM, Christoph Hellwig wrote:
> On Wed, Dec 10, 2025 at 09:44:52AM -0800, Bart Van Assche wrote:
>> On 12/9/25 10:48 PM, Christoph Hellwig wrote:
>>> As mentioned last round, why are you even calling into the crypto
>>> code here?  Calling that for a request without a crypt context,
>>> which includes all of them that do not transfer any data makes no
>>> sense to start with.
>>
>> ufshcd_prepare_lrbp_crypto() only has one caller. Moving the new test
>> from inside ufshcd_prepare_lrbp_crypto() into its caller should be easy.
> 
> I don't think callers vs calle is the important part here.  It is to
> check if any actual data is tranferred instead of special casing EH
> commands.

Hi Christoph,

Do you agree with the following?

(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:

		scmd->sdb.length = min_t(unsigned, SCSI_SENSE_BUFFERSIZE,
					 sense_bytes);
		sg_init_one(&ses->sense_sgl, scmd->sense_buffer,
			    scmd->sdb.length);
		scmd->sdb.table.sgl = &ses->sense_sgl;

(b) In general in the Linux kernel it is strongly preferred to fix the
     root cause of a bug rather than to implement a workaround. This is
     preferred because it makes kernel code easier to maintain and
     reduces the chance that new bugs are introduced.

(c) Disabling encryption in the UFS driver if a command has been
     submitted by the SCSI error handler is a workaround. Patch [1] fixes
     the root cause of the problem, namely the SCSI error handler not
     setting the encryption fields in struct request correctly. We prefer
     [1] because UFS devices that support one million IOPS are expected
     to arrive soon (early 2026). Hence the importance of keeping the hot
     path in the UFS driver fast.

Thanks,

Bart.

[1] [PATCH v2 1/1] scsi: core: Fix error handler encryption support
  
(https://lore.kernel.org/linux-scsi/20251203073310.2248956-1-powenkao@google.com/)

  reply	other threads:[~2025-12-15 16:47 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 [this message]
2025-12-16 10:44         ` Christoph Hellwig
2025-12-16 17:57           ` Bart Van Assche

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=54d824db-ec39-447c-8eab-6c2ce4ca87a6@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