diff options
| author | Ezra Peisach <epeisach@mit.edu> | 2008-08-14 04:44:44 +0000 |
|---|---|---|
| committer | Ezra Peisach <epeisach@mit.edu> | 2008-08-14 04:44:44 +0000 |
| commit | f4c8a41e68aa417d6ab95a41333507cf34f3f89c (patch) | |
| tree | c0745f6fb5f2460a3a85bb3f31190ba9604ae5b0 /src/kdc | |
| parent | 9b04053eddd676de68cde9e5c549409aee2282b3 (diff) | |
| download | krb5-f4c8a41e68aa417d6ab95a41333507cf34f3f89c.tar.gz krb5-f4c8a41e68aa417d6ab95a41333507cf34f3f89c.tar.xz krb5-f4c8a41e68aa417d6ab95a41333507cf34f3f89c.zip | |
krb5_fcc_resolve file locking error on malloc failuer
In krb5_fcc_resolve, on malloc failure, the data->lock mutex needs to
be destroyed. Unfortunately, this is done with the mutex is still locked. When thread debugging code is enabled, this results in aeg fault.
Also - in krb5_fcc_generate_new, a strdup failure would result in the
krb5int_cc_file_mutex being unlocked twice.
[I have a modified version of valgrind in which I can signal after a
certain number of mallocs for it to fail - I vary the allocation
number from 1300 to 0 - and see what breaks - some memory leaks will
be fixed separately]
ticket: new
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@20653 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/kdc')
0 files changed, 0 insertions, 0 deletions