From: Jiri Slaby Subject: ecryptfs lock loop Date: Tue, 14 Apr 2009 21:36:04 +0200 Message-ID: <49E4E5A4.80109@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: kirkland@canonical.com, ecryptfs-devel@lists.launchpad.net, linux-fsdevel@vger.kernel.org, Linux kernel mailing list , xatrix101@gmail.com To: tyhicks@linux.vnet.ibm.com Return-path: Received: from mail-ew0-f165.google.com ([209.85.219.165]:34163 "EHLO mail-ew0-f165.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765AbZDNTgJ (ORCPT ); Tue, 14 Apr 2009 15:36:09 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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