linux-kernel - Re: [PATCH] scsi: libsas: Fix dev_list race conditions with proper locking

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: <e59ff23b-81d3-41b7-ac25-ab886a3379bf@huawei.com>
Date: Fri, 30 Jan 2026 16:27:11 +0800
From: Jason Yan <yanaijie@...wei.com>
To: Chaohai Chen <wdhh6@...yun.com>, <john.g.garry@...cle.com>,
	<James.Bottomley@...senPartnership.com>, <martin.petersen@...cle.com>,
	<dlemoal@...nel.org>, <johannes.thumshirn@....com>, <mingo@...nel.org>,
	<cassel@...nel.org>, <tglx@...nel.org>
CC: <linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scsi: libsas: Fix dev_list race conditions with proper
 locking

Hi,

在 2026/1/29 17:38, Chaohai Chen 写道:
> Multiple functions in libsas were accessing port->dev_list without
> proper locking, leading to potential race conditions that could cause:
> - Use-after-free when devices are removed during list traversal
> - List corruption from concurrent modifications
> - System crashes from accessing freed memory

libsas events are processed in orderd workqueue. Do you have a crash log?

Thanks,
祝一切顺利