add chdir-notify API
If one part of the code does a permanent chdir(), then this invalidates any relative paths that may be held by other parts of the code. For example, setup_work_tree() moves us to the top of the working tree, which may invalidate a previously stored relative gitdir. We've hacked around this case by teaching setup_work_tree() to re-run set_git_dir() with an adjusted path, but this stomps all over the idea of module boundaries. setup_work_tree() shouldn't have to know all of the places that need to be fed an adjusted path. And indeed, there's at least one other place (the refs code) which needs adjusting. Let's provide an API to let code that stores relative paths "subscribe" to updates to the current working directory. This means that callers of chdir() don't need to know about all subscribers ahead of time; they can simply consult a dynamically built list. Note that our helper function to reparent relative paths uses the simple remove_leading_path(). We could in theory use the much smarter relative_path(), but that led to some problems as described in 41894ae3a3 (Use simpler relative_path when set_git_dir, 2013-10-14). Since we're aiming to replace the setup_work_tree() code here, let's follow its lead. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Mar 30, 2018 at 14:35 UTC
2b5ed373656c225d2baea09da130531fe7275fa2
3 files changed
+167
Makefile
+1
@@ -772,6 +772,7 @@ LIB_OBJS += branch.o
772
LIB_OBJS += bulk-checkin.o
773
LIB_OBJS += bundle.o
774
LIB_OBJS += cache-tree.o
775
+LIB_OBJS += chdir-notify.o
776
LIB_OBJS += checkout.o
777
LIB_OBJS += color.o
778
LIB_OBJS += column.o
chdir-notify.c
new
+93
@@ -0,0 +1,93 @@
1
+#include "cache.h"
2
+#include "chdir-notify.h"
3
+#include "list.h"
4
+#include "strbuf.h"
5
+
6
+struct chdir_notify_entry {
7
+ const char *name;
8
+ chdir_notify_callback cb;
9
+ void *data;
10
+ struct list_head list;
11
+};
12
+static LIST_HEAD(chdir_notify_entries);
13
+
14
+void chdir_notify_register(const char *name,
15
+ chdir_notify_callback cb,
16
+ void *data)
17
+{
18
+ struct chdir_notify_entry *e = xmalloc(sizeof(*e));
19
+ e->name = name;
20
+ e->cb = cb;
21
+ e->data = data;
22
+ list_add_tail(&e->list, &chdir_notify_entries);
23
+}
24
+
25
+static void reparent_cb(const char *name,
26
+ const char *old_cwd,
27
+ const char *new_cwd,
28
+ void *data)
29
+{
30
+ char **path = data;
31
+ char *tmp = *path;
32
+
33
+ if (!tmp)
34
+ return;
35
+
36
+ *path = reparent_relative_path(old_cwd, new_cwd, tmp);
37
+ free(tmp);
38
+
39
+ if (name) {
40
+ trace_printf_key(&trace_setup_key,
41
+ "setup: reparent %s to '%s'",
42
+ name, *path);
43
+ }
44
+}
45
+
46
+void chdir_notify_reparent(const char *name, char **path)
47
+{
48
+ chdir_notify_register(name, reparent_cb, path);
49
+}
50
+
51
+int chdir_notify(const char *new_cwd)
52
+{
53
+ struct strbuf old_cwd = STRBUF_INIT;
54
+ struct list_head *pos;
55
+
56
+ if (strbuf_getcwd(&old_cwd) < 0)
57
+ return -1;
58
+ if (chdir(new_cwd) < 0) {
59
+ int saved_errno = errno;
60
+ strbuf_release(&old_cwd);
61
+ errno = saved_errno;
62
+ return -1;
63
+ }
64
+
65
+ trace_printf_key(&trace_setup_key,
66
+ "setup: chdir from '%s' to '%s'",
67
+ old_cwd.buf, new_cwd);
68
+
69
+ list_for_each(pos, &chdir_notify_entries) {
70
+ struct chdir_notify_entry *e =
71
+ list_entry(pos, struct chdir_notify_entry, list);
72
+ e->cb(e->name, old_cwd.buf, new_cwd, e->data);
73
+ }
74
+
75
+ strbuf_release(&old_cwd);
76
+ return 0;
77
+}
78
+
79
+char *reparent_relative_path(const char *old_cwd,
80
+ const char *new_cwd,
81
+ const char *path)
82
+{
83
+ char *ret, *full;
84
+
85
+ if (is_absolute_path(path))
86
+ return xstrdup(path);
87
+
88
+ full = xstrfmt("%s/%s", old_cwd, path);
89
+ ret = xstrdup(remove_leading_path(full, new_cwd));
90
+ free(full);
91
+
92
+ return ret;
93
+}
chdir-notify.h
new
+73
@@ -0,0 +1,73 @@
1
+#ifndef CHDIR_NOTIFY_H
2
+#define CHDIR_NOTIFY_H
3
+
4
+/*
5
+ * An API to let code "subscribe" to changes to the current working directory.
6
+ * The general idea is that some code asks to be notified when the working
7
+ * directory changes, and other code that calls chdir uses a special wrapper
8
+ * that notifies everyone.
9
+ */
10
+
11
+/*
12
+ * Callers who need to know about changes can do:
13
+ *
14
+ * void foo(const char *old_path, const char *new_path, void *data)
15
+ * {
16
+ * warning("switched from %s to %s!", old_path, new_path);
17
+ * }
18
+ * ...
19
+ * chdir_notify_register("description", foo, data);
20
+ *
21
+ * In practice most callers will want to move a relative path to the new root;
22
+ * they can use the reparent_relative_path() helper for that. If that's all
23
+ * you're doing, you can also use the convenience function:
24
+ *
25
+ * chdir_notify_reparent("description", &my_path);
26
+ *
27
+ * Whenever a chdir event occurs, that will update my_path (if it's relative)
28
+ * to adjust for the new cwd by freeing any existing string and allocating a
29
+ * new one.
30
+ *
31
+ * Registered functions are called in the order in which they were added. Note
32
+ * that there's currently no way to remove a function, so make sure that the
33
+ * data parameter remains valid for the rest of the program.
34
+ *
35
+ * The "name" argument is used only for printing trace output from
36
+ * $GIT_TRACE_SETUP. It may be NULL, but if non-NULL should point to
37
+ * storage which lasts as long as the registration is active.
38
+ */
39
+typedef void (*chdir_notify_callback)(const char *name,
40
+ const char *old_cwd,
41
+ const char *new_cwd,
42
+ void *data);
43
+void chdir_notify_register(const char *name, chdir_notify_callback cb, void *data);
44
+void chdir_notify_reparent(const char *name, char **path);
45
+
46
+/*
47
+ *
48
+ * Callers that want to chdir:
49
+ *
50
+ * chdir_notify(new_path);
51
+ *
52
+ * to switch to the new path and notify any callbacks.
53
+ *
54
+ * Note that you don't need to chdir_notify() if you're just temporarily moving
55
+ * to a directory and back, as long as you don't call any subscribed code in
56
+ * between (but it should be safe to do so if you're unsure).
57
+ */
58
+int chdir_notify(const char *new_cwd);
59
+
60
+/*
61
+ * Reparent a relative path from old_root to new_root. For example:
62
+ *
63
+ * reparent_relative_path("/a", "/a/b", "b/rel");
64
+ *
65
+ * would return the (newly allocated) string "rel". Note that we may return an
66
+ * absolute path in some cases (e.g., if the resulting path is not inside
67
+ * new_cwd).
68
+ */
69
+char *reparent_relative_path(const char *old_cwd,
70
+ const char *new_cwd,
71
+ const char *path);
72
+
73
+#endif /* CHDIR_NOTIFY_H */