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-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
