linux-kernel - Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <w52ajxs5rszlw5tyuezgf5ym2sz5nqnqlm2bbvbfvqy2rbth6v@jttotxort4rb>
Date: Fri, 31 Oct 2025 13:45:17 +0530
From: Manivannan Sadhasivam <mani@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>, 
	bjorn.andersson@....qualcomm.com, arnd@...db.de, linux-kernel@...r.kernel.org, 
	linux-arm-msm@...r.kernel.org
Subject: Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and
 Block Inline encryption drivers

On Fri, Oct 31, 2025 at 08:45:38AM +0100, Krzysztof Kozlowski wrote:
> On 31/10/2025 07:24, Manivannan Sadhasivam wrote:
> > On Thu, Oct 30, 2025 at 08:48:48PM +0100, Krzysztof Kozlowski wrote:
> >> On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
> >>> These drivers will allow using the crypto functionalities of the UFS
> >>> device, like Inline Crypto Encryption. Both of these drivers are of type
> >>> 'bool', so they cannot be built as modules.
> >>
> >> Is there any device benefiting from these? Which board?
> >>
> > 
> > All ICE capable Qcom UFS based boards.
> > 
> >>>
> >>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
> >>> Signed-off-by: Manivannan Sadhasivam <mani@...nel.org>
> >>
> >> You do not need the second tag. You send it via oss.qualcomm.com which
> >> is still valid.
> >>
> > 
> > Yes, I know. But I was having some issue in sending email through
> > oss.qualcomm.com. Now it got fixed in the RESEND patch, but forgot to remove my
> > korg s-o-b.
> 
> 
> You do not need second sob when sending through korg. Your previous
> identity was still valid. It's used only when old identity is considered
> revoked.
> 

Hmm. I thought the s-o-b should always match the maildomain from which the patch
was sent.

Thanks for clarifying.

- Mani

-- 
மணிவண்ணன் சதாசிவம்