From: Jiri Slaby <jirislaby@gmail.com>
To: tyhicks@linux.vnet.ibm.com
Cc: kirkland@canonical.com, ecryptfs-devel@lists.launchpad.net,
linux-fsdevel@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
xatrix101@gmail.com
Subject: ecryptfs lock loop
Date: Tue, 14 Apr 2009 21:36:04 +0200 [thread overview]
Message-ID: <49E4E5A4.80109@gmail.com> (raw)
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
next reply other threads:[~2009-04-14 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 19:36 Jiri Slaby [this message]
2009-04-15 15:40 ` ecryptfs lock loop Tyler Hicks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E4E5A4.80109@gmail.com \
--to=jirislaby@gmail.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=kirkland@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@linux.vnet.ibm.com \
--cc=xatrix101@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox