linux-kernel - Re: [PATCH 0/1] Fix not fully initialized SCSI commands

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: <d5de0d00881b66cf7591ce5af4cc73c14f4d65ba.camel@HansenPartnership.com>
Date: Mon, 24 Mar 2025 07:52:19 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Anastasia Kovaleva <a.kovaleva@...ro.com>, martin.petersen@...cle.com, 
	hare@...e.de, axboe@...nel.dk
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org, linux@...ro.com
Subject: Re: [PATCH 0/1] Fix not fully initialized SCSI commands

On Mon, 2025-03-24 at 11:49 +0300, Anastasia Kovaleva wrote:
> We have encountered the following type of logs on initiators:

Hey, Anna,

Just so you know what's going on, Yadro is on the US SDN sanctions
list:

https://sanctionssearch.ofac.treas.gov/Details.aspx?id=39140

Which means that under the latest LF guidance:

https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions

We could take your patch as is, but we can't discuss changing it with
you (Point 3: avoid two way engagement).

Really sorry about this,

Regards,

James Bottomley