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: <57e07c9b-b8fe-49b6-9ad5-ef6ba0e763c7@sezginduran.net>
Date: Fri, 23 Jan 2026 17:02:27 +0300
From: Ahmet Sezgin Duran <ahmet@...ginduran.net>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mmc: pxamci: do not complete requests under host spinlock

On 1/23/26 2:58 PM, Ulf Hansson wrote:

 > I was too quick here. Is this really a problem that you have tested or
 > just something that you believe is the right thing to do?

The latter. I thought this could be an issue and tried to handle it 
defensively.

 > Other drivers are holding spinlocks too when they call the mmc core to
 > complete requests. In principle it depends on how the host implements
 > locking, whether it's fine or not. For pxamci, I think it should be
 > fine to keep the lock held as the core will only kick a completion
 > variable in this case.
 >
 > That said, I am going to drop this

Got it, thanks for the clarification.

Regards,

Ahmet Sezgin Duran

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ