From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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 02:44:57 -0800 [thread overview]
Message-ID: <aUE4Kf73OxxO7r-K@infradead.org> (raw)
In-Reply-To: <54d824db-ec39-447c-8eab-6c2ce4ca87a6@acm.org>
On Mon, Dec 15, 2025 at 08:47:03AM -0800, Bart Van Assche wrote:
> > 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:
This still does not actually transfer data to the media, and thus
is not affected by inline encryption.
next prev parent reply other threads:[~2025-12-16 10:44 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 [this message]
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=aUE4Kf73OxxO7r-K@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.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