linux-kernel - Re: [PATCH 1/4] scsi: ufs: core: Introduce a new host register lock

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <85d2cb9b-75ba-4ab3-a50d-0f8161456fcb@acm.org>
Date: Mon, 21 Oct 2024 11:35:42 -0700
From: Bart Van Assche <bvanassche@....org>
To: Avri Altman <avri.altman@....com>,
 "Martin K . Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] scsi: ufs: core: Introduce a new host register lock

On 10/21/24 5:03 AM, Avri Altman wrote:
> Introduce a new host register read/write lock.  Use it to protect access
> to the task management doorbell register: UTMRLDBR.  This is not the
> UTRLDBR which is already protected by its own outstanding_lock.

Why is this necessary? I think it is allowed to submit host controller
reads and writes simultaneously from different threads. Only 
read/modify/writes have to be serialized.

Thanks,

Bart.