From 53d6d0d64e96b84b57b7446a787e683312e2a529 Mon Sep 17 00:00:00 2001 From: Will Fiveash Date: Wed, 19 Mar 2014 16:48:15 -0500 Subject: [PATCH] Always stat profile files after reopening them Some applications write a profile file and then immediately use it via a krb5_context. If we have a cached copy of the profile we wrote, make sure to update it by forcing a stat when we reuse an existing prf_data_t object. [ghudson@mit.edu: commit message] ticket: 7884 --- src/util/profile/prof_file.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/util/profile/prof_file.c b/src/util/profile/prof_file.c index 76411db8ab..5611233704 100644 --- a/src/util/profile/prof_file.c +++ b/src/util/profile/prof_file.c @@ -249,6 +249,7 @@ errcode_t profile_open_file(const_profile_filespec_t filespec, } if (data) { data->refcount++; + data->last_stat = 0; /* Make sure to stat when updating. */ k5_mutex_unlock(&g_shared_trees_mutex); retval = profile_update_file_data(data, NULL); free(expanded_filename); -- 2.47.2