summaryrefslogtreecommitdiff
path: root/src/nm-session-monitor.c
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2017-11-15 16:06:43 +0100
committerThomas Haller <thaller@redhat.com>2017-11-16 11:49:52 +0100
commit93adadbdcbbccfeafb8523b129f103bb5b23f7d5 (patch)
treeba659102aeb347cb6c8689713aa15e7e2d052068 /src/nm-session-monitor.c
parentb58481b31ec5785d208a7b11df5b05fc50c158e2 (diff)
downloadNetworkManager-93adadbdcbbccfeafb8523b129f103bb5b23f7d5.tar.gz
all: use nm_direct_hash() instead of g_direct_hash()
We also do this for libnm, where it causes visible changes in behavior. But if somebody would rely on the hashing implementation for hash tables, it would be seriously flawed.
Diffstat (limited to 'src/nm-session-monitor.c')
-rw-r--r--src/nm-session-monitor.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nm-session-monitor.c b/src/nm-session-monitor.c
index 045c29af4c..bbf27acdbb 100644
--- a/src/nm-session-monitor.c
+++ b/src/nm-session-monitor.c
@@ -258,7 +258,7 @@ ck_init (NMSessionMonitor *monitor)
if (g_file_query_exists (file, NULL)) {
if ((monitor->ck.monitor = g_file_monitor_file (file, G_FILE_MONITOR_NONE, NULL, &error))) {
- monitor->ck.cache = g_hash_table_new_full (NULL, NULL, NULL, g_free);
+ monitor->ck.cache = g_hash_table_new_full (nm_direct_hash, NULL, NULL, g_free);
g_signal_connect (monitor->ck.monitor,
"changed",
G_CALLBACK (ck_changed),