linux-kernel - mutex ownership tracking

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

Message-ID: <CAH9_wRPJaCXixCuTDOepvn107jfLST9jgF14iXAb-QPtphHWsQ@mail.gmail.com>
Date:	Mon, 20 Jan 2014 21:40:56 +0530
From:	Sriram V <vshrirama@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: mutex ownership tracking

Hello,

What is the importance of ownership tracking of mutex? Why is it
mandatory that the task which
locked must unlock it to escape lockdep.


-- 
Regards,
Sriram
--
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/