[15859] in Kerberos-V5-bugs

home help back first fref pref prev next nref lref last post

[krbdev.mit.edu #8632] make check breaks in AIX

daemon@ATHENA.MIT.EDU (Greg Hudson via RT)
Tue Jan 16 11:40:51 2018

Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: "Greg Hudson via RT" <rt-comment@KRBDEV-PROD-APP-1.mit.edu>
In-Reply-To: <rt-8632@krbdev.mit.edu>
Message-ID: <rt-8632-48205.4.28162197981017@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #8632'":;
Date: Tue, 16 Jan 2018 11:40:18 -0500 (EST)
Reply-To: rt-comment@KRBDEV-PROD-APP-1.mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu

I see two potential candidates for the failing k5_mutex_lock() call, 
based on the k5_mutex_lock() calls which occur in test_et after the 
last line of output is written:

1. com_err_terminate() -> krb5int_key_delete() -> 
k5_mutex_lock(&key_lock)
2. com_err_terminate() -> k5_mutex_lock(&et_list_lock)

Candidate 2 seems unlikely as the destruction of et_list_lock clearly 
happens after the k5_mutex_lock() call.

For candidate 1, If the libkrb5support finalizer runs before the 
libcom_err finalizer, key_lock would be destroyed before we lock it 
and we would get an EINVAL.  Since AIX doesn't seem to do shared 
library dependencies, I guess it's not surprising that it would also 
not do library finalizer ordering.  The best workaround is probably 
to avoid running library finalizers on AIX.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs

home help back first fref pref prev next nref lref last post