linux-kernel - RE: [tpmdd-devel] [PATCH] TPM: Let the tpm char device be openable multiple times

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

Message-ID: <74A44E99E3274B4CB570415926B37D440ED140@MUCSE501.eu.infineon.com>
Date:	Mon, 15 Oct 2012 08:35:09 +0000
From:	<Peter.Huewe@...ineon.com>
To:	<jgunthorpe@...idianresearch.com>, <key@...ux.vnet.ibm.com>
CC:	<tpmdd-devel@...ts.sourceforge.net>, <linux-kernel@...r.kernel.org>
Subject: RE: [tpmdd-devel] [PATCH] TPM: Let the tpm char device be openable
	multiple times

-----Original Message-----
> From: Jason Gunthorpe [mailto:jgunthorpe@...idianresearch.com] 

> Using open/close is an interesting idea, but it wouldn't work. open()
> is coded to return EBUSY if another process has it open, rather than
> block, and spinning on open would be unacceptable.

Hmm, maybe write a small pass through program which opens /dev/tpm once and accepts its data via a socket or pipe?

Thanks,
Peter


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