linux-kernel - [next] possible recursive locking in autofs4

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

Date:	Sun, 15 Jan 2012 16:59:12 -0600
From:	Milton Miller <miltonm@....com>
To:	Martin Nyhus <martin.nyhus@....com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: [next] possible recursive locking in autofs4_write

> Looks like mutex_lock should have been mutex_unlock in commit d668dc56
> (autofs4: deal with autofs4_write/autofs4_write races) at
> fs/autofs4/waitq.c:79, but I don't really know the code so if someone
> could have a look that would be great.
> 

Yes, see http://lkml.indiana.edu/hypermail/linux/kernel/1201.1/02312.html

milton
--
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/