aboutsummaryrefslogtreecommitdiff
path: root/src/util
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2016-06-23 12:01:56 -0400
committerGreg Hudson <ghudson@mit.edu>2016-07-01 14:27:23 -0400
commit32a05995ff9df0d5ef8aff0d020900a37747670d (patch)
tree3f308e497d7ef18ff7aafbe9b35b6672254fe833 /src/util
parent4131988dec0199287765e1875fe0bbd375656a62 (diff)
downloadkrb5-32a05995ff9df0d5ef8aff0d020900a37747670d.zip
krb5-32a05995ff9df0d5ef8aff0d020900a37747670d.tar.gz
krb5-32a05995ff9df0d5ef8aff0d020900a37747670d.tar.bz2
Fix profile_flush_to_file() state corruption
In write_data_to_file(), do not clear the profile data object's flags. If the call to this function resulted from profile_flush_to_file(), we do not want to clear the DIRTY flag, and we especially do not want to clear the SHARED flag for a data object which is part of g_shared_trees. Instead, clear the DIRTY flag in profile_flush_file_data(). Add a test case to prof_test1 to exercise the bug in unfixed code. Also modify test1 to abandon the altered profile after flushing it to a file, to preserve the external behavior of the script before this fix. ticket: 8431 target_version: 1.14-next tags: pullup
Diffstat (limited to 'src/util')
-rw-r--r--src/util/profile/prof_file.c2
-rw-r--r--src/util/profile/prof_test122
2 files changed, 22 insertions, 2 deletions
diff --git a/src/util/profile/prof_file.c b/src/util/profile/prof_file.c
index d774593..907c119 100644
--- a/src/util/profile/prof_file.c
+++ b/src/util/profile/prof_file.c
@@ -473,7 +473,6 @@ static errcode_t write_data_to_file(prf_data_t data, const char *outfile,
}
}
- data->flags = 0;
retval = 0;
errout:
@@ -509,6 +508,7 @@ errcode_t profile_flush_file_data(prf_data_t data)
}
retval = write_data_to_file(data, data->filespec, 0);
+ data->flags &= ~PROFILE_FILE_DIRTY;
k5_mutex_unlock(&data->lock);
return retval;
}
diff --git a/src/util/profile/prof_test1 b/src/util/profile/prof_test1
index d0bb187..984eb3b 100644
--- a/src/util/profile/prof_test1
+++ b/src/util/profile/prof_test1
@@ -40,7 +40,7 @@ proc test1 {} {
#profile_iterator_free $iter
catch {file delete $wd/test3.ini}
profile_flush_to_file $p $wd/test3.ini
- profile_release $p
+ profile_abandon $p
if $verbose { puts "Reloading new profile" }
set p [profile_init_path $wd/test3.ini]
@@ -318,6 +318,25 @@ proc test8 {} {
puts "OK: test8: relation order in the presence of deletions"
}
+proc test9 {} {
+ global wd verbose
+
+ # Regression test for #8431: profile_flush_to_file erroneously
+ # cleared the DIRTY and SHARED flags from the data object, which
+ # could lead to a dangling reference in g_shared_trees on release.
+ set p [profile_init_path $wd/test2.ini]
+ catch {file delete $wd/test3.ini}
+ profile_flush_to_file $p $wd/test3.ini
+ profile_release $p
+
+ # If a dangling reference was created in g_shared_trees, the next
+ # profile open will trigger an assertion failure.
+ set p [profile_init_path $wd/test2.ini]
+ profile_release $p
+
+ puts "OK: test9: profile_flush_to_file with no changes"
+}
+
test1
test2
test3
@@ -326,5 +345,6 @@ test5
test6
test7
test8
+test9
exit 0