Skip Menu |
 

To: krb5-bugs@mit.edu
From: Ken Raeburn <raeburn@mit.edu>
Date: Wed, 12 Jan 2005 20:28:05 -0500
Subject: locking bug in file ccache
There seems to be a locking bug in cc_file.c where one thread,
changing the "OPENCLOSE" mode, wants to release disk_file_lock when
it's locked by a different thread. This seems to show up on x86-linux
under valgrind with Jeff Altman's modified multithreaded gss sample
program, but not without valgrind.

My locking strategy overall in that file is poorly thought out and
needs some work (and documentation). This should be fixed for 1.4.

Ken
From: raeburn@mit.edu
Subject: CVS Commit
* cc_file.c (struct _krb5_fcc_data): Fields disk_file_lock, file_is_locked
deleted.
(krb5_fcc_open_file, krb5_fcc_close_file, dereference, krb5_fcc_resolve,
krb5_fcc_generate_new, krb5_fcc_set_flags): Don't set or check them.


To generate a diff of this commit:



cvs diff -r5.154 -r5.155 krb5/src/lib/krb5/ccache/ChangeLog
cvs diff -r5.43 -r5.44 krb5/src/lib/krb5/ccache/cc_file.c
From: tlyu@mit.edu
Subject: CVS Commit
pullup from trunk


To generate a diff of this commit:



cvs diff -r5.147.4.5 -r5.147.4.6 krb5/src/lib/krb5/ccache/ChangeLog
cvs diff -r5.41.4.1 -r5.41.4.2 krb5/src/lib/krb5/ccache/cc_file.c