We are seeing many of these crashes. The cause is a null pointer in
libpthread from a bad argument to MUTEX_LOCK in tspi/rpc/hosttable.c.
Any idea? I am reluctant to blame the caller (opencryptoki) because
it's unlikely the multithreading details are exposed to it, but you
never know.
Thanks!
struct host_table_entry *
get_table_entry(TSS_HCONTEXT tspContext)
{
struct host_table_entry *index = NULL;
MUTEX_LOCK(ht->lock);
0x7747bc1d [libpthread-2.10.1.so + 0x00007c1d]
0x77167c98 [libtspi.so.1.1.3 - rpc/hosttable.c:161] get_table_entry
0x77167a04 [libtspi.so.1.1.3 - rpc/tcs_api.c:95] RPC_CloseContext
0x77161a08 [libtspi.so.1.1.3 - tspi_context.c:49]
Tspi_Context_Close
0x771f0cbd [libpkcs11_tpm.so.0.0.0 - tpm_specific.c:2004]
token_specific_final
0x771d02b9 [libpkcs11_tpm.so.0.0.0 - new_host.c:556]
SC_Finalize
0x772c6689 [libopencryptoki.so.0.0.0 - api_interface.c:1912]
C_Finalize
0x772c6719 [libopencryptoki.so.0.0.0 - api_interface.c:3232]
Call_Finalize
0x772c678c [libopencryptoki.so.0.0.0 - api_interface.c:5208]
api_fini
0x772bf497 [libopencryptoki.so.0.0.0 + 0x00002497]
0x772c80af [libopencryptoki.so.0.0.0 + 0x0000b0af]
0x776c5ad5 [ld-2.10.1.so + 0x0000ead5]
0x7734e148 [libc-2.10.1.so + 0x0002d148]
0x7734e1ae [libc-2.10.1.so + 0x0002d1ae]
0x77337a9d [libc-2.10.1.so + 0x00016a9d]
0x776e3350 [wpa_supplicant + 0x0000e350]
0x777306ff [wpa_supplicant + 0x0005b6ff]
0x776c58af [ld-2.10.1.so + 0x0000e8af]
------------------------------------------------------------------------------
Achieve Improved Network Security with IP and DNS Reputation.
Defend against bad network traffic, including botnets, malware,
phishing sites, and compromised hosts - saving your company time,
money, and embarrassment. Learn More!
http://p.sf.net/sfu/hpdev2dev-nov
_______________________________________________
TrouSerS-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/trousers-users
