linux-kernel - iwl: potential deadlock?

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

Message-ID: <4A5B8C60.9000600@gmail.com>
Date:	Mon, 13 Jul 2009 21:34:56 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	yi.zhu@...el.com
CC:	reinette.chatre@...el.com, linux-wireless@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: iwl: potential deadlock?

Hi,

we found a potential deadlock in iwl code by our tool.

Can this happen:
iwl_update_tkip_key()
-> spin_lock_irqsave(&priv->sta_lock)
-> iwl_send_add_sta()
   -> iwl_sta_ucode_activate()
      -> spin_lock_irqsave(&priv->sta_lock)
?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/