p11-kit.git - Clone of https://github.com/p11-glue/p11-kit

	Commit message (Collapse)	Author	Age	Files	Lines
*	library: Deinit p11_virtual_mutex	Daiki Ueno	2017-02-16	1	-0/+1
\| \| \| \| \|	Follow-up fix for commit 4d228aa0, which forgot to clear p11_virtual_mutex on library finalization.
*	virtual: Move mutex into p11_library_init()	Daiki Ueno	2017-02-14	1	-0/+3
\| \| \| \| \| \| \| \| \|	We used to provide p11_virtual_fixed_{,un}init() to only initialize a mutex used in virtual.c. That required all the tests calling virtual functions to call p11_virtual_fixed_{,un}init() in main(). For simplicity, move the mutex variable initialization into p11_library_init().
*	p11-kit: Use pthread_atfork() in a safe manner	Stef Walter	2014-10-03	1	-0/+11
\| \| \| \| \| \| \| \| \| \| \| \| \|	Instead of trying to perform actions in pthread_atfork() which are not async-signal-safe, just increment a counter so we can later tell if the process has forked. Note this does not make it safe to mix threads and forking without immediately execing. This is a far broader problem that p11-kit, however we now do the right thing when fork+exec is used from a thread. https://bugs.freedesktop.org/show_bug.cgi?id=84567
*	Fix uninitialized p11_library_once	manphiz@gmail.com	2013-05-28	1	-1/+1
\| \| \| \|	https://bugs.freedesktop.org/show_bug.cgi?id=57714
*	Don't use free() on memory allocated by LocalFree()	Stef Walter	2013-04-03	1	-1/+1
\| \| \| \|	ihttps://bugs.freedesktop.org/show_bug.cgi?id=63046
*	Separate library init from message code	Stef Walter	2013-04-03	1	-71/+14
\| \| \| \| \| \| \| \| \| \| \|	Put library init/uninit code its into their own statically linked library so that they don't get linked into the p11-kit executable. Refactor the message code so that the library initialization can plug in its per thread message buffer. https://bugs.freedesktop.org/show_bug.cgi?id=63046
*	Don't use library locks from p11-kit tool	Stef Walter	2013-04-03	1	-4/+0
\| \| \| \| \| \| \|	The global library p11_library_mutex is for libraries to use, so don't use it from any code in common/, which is also used by the p11-kit tool https://bugs.freedesktop.org/show_bug.cgi?id=63046
*	Don't shove messages into debug output if they're already displayed	Stef Walter	2013-03-08	1	-2/+2
\|
*	Fix syntax errors in OS_WIN32 ifdefs	Stef Walter	2013-03-03	1	-3/+3
\|
*	Only do shared object and DLL initialization in libraries	Stef Walter	2013-02-20	1	-49/+11
\| \| \| \| \| \|	Don't do library initialization on shared object load when not running in a library. We'll want to plug into this and do different things per library in the future.
*	Add internal function for turning on messages	Stef Walter	2013-02-05	1	-0/+8
\| \| \| \|	To be used from tests
*	Use the stdbool.h C99 bool type	Stef Walter	2013-01-23	1	-2/+2
\| \| \| \| \| \|	It was getting really wild knowing whether a function returning an int would return -1 on failure or 0 or whether the int return value was actually a number etc..
*	Only initialize p11-kit libraries once	Stef Walter	2013-01-09	1	-4/+10
\| \| \| \|	* Make the gcc constructor call p11_library_init_once()
*	Move debug and library code into the common/ subdirectory	Stef Walter	2013-01-09	1	-0/+286
	Start using p11_ as our internal prefix rather than _p11_. We explicitly export p11_kit_ so this is fine as far as visibility. Move the threading, mutex, and module compat, dict, and array code into the common directory too. Take this opportunity to clean up a bit of internal API as well, since so many lines are being touched internally.