linux-kernel - ecryptfs lock loop

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: <49E4E5A4.80109@gmail.com>
Date:	Tue, 14 Apr 2009 21:36:04 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	tyhicks@...ux.vnet.ibm.com
CC:	kirkland@...onical.com, ecryptfs-devel@...ts.launchpad.net,
	linux-fsdevel@...r.kernel.org,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	xatrix101@...il.com
Subject: ecryptfs lock loop

Hi,

one student (in CC) found out a suspicioous locking dependence in
ecryptfs code while debugging/running a static lockdep analyzer.

I'm unable to say whether it is only a theoretical issue or a real bug,
any ideas?

Here it comes:

function ecryptfs_send_message:
------------------------------
ecryptfs_daemon_hash_mux <- ecryptfs_msg_ctx_lists_mux
(in function ecryptfs_send_message_locked)

function ecryptfs_wait_for_response:
-----------------------------------
cryptfs_msg_ctx_lists_mux <- msg_ctx->mux

function ecryptfs_process_response:
----------------------------------
msg_ctx->mux <- ecryptfs_daemon_hash_mux


<- means lock dependency
--
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/