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
| ||
|
Message-ID: <20231007151328.GD831234@kernel.org> Date: Sat, 7 Oct 2023 17:13:28 +0200 From: Simon Horman <horms@...nel.org> To: Chengfeng Ye <dg573847474@...il.com> Cc: 3chas3@...il.com, davem@...emloft.net, linux-atm-general@...ts.sourceforge.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2 2/2] atm: solos-pci: Fix potential deadlock on &tx_queue_lock On Thu, Oct 05, 2023 at 07:49:17AM +0000, Chengfeng Ye wrote: > As &card->tx_queue_lock is acquired under softirq context along the > following call chain from solos_bh(), other acquisition of the same > lock inside process context should disable at least bh to avoid double > lock. > > <deadlock #2> > pclose() > --> spin_lock(&card->tx_queue_lock) > <interrupt> > --> solos_bh() > --> fpga_tx() > --> spin_lock(&card->tx_queue_lock) > > This flaw was found by an experimental static analysis tool I am > developing for irq-related deadlock. > > To prevent the potential deadlock, the patch uses spin_lock_irqsave() > on &card->tx_queue_lock under process context code consistently to > prevent the possible deadlock scenario. > > Fixes: 213e85d38912 ("solos-pci: clean up pclose() function") > Signed-off-by: Chengfeng Ye <dg573847474@...il.com> > --- > V2: add fix tag, and split into two patches Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists