[PATCH] free_ref_entry(): do not trigger reading of loose refs
From: <hidden>
Date: 2016-06-15 22:53:51
Subsystem:
the rest · Maintainer:
Linus Torvalds
From: <hidden>
Date: 2016-06-15 22:53:51
Subsystem:
the rest · Maintainer:
Linus Torvalds
From: Michael Haggerty <redacted> Do not call get_ref_dir() from within free_ref_entry(), because that triggers the reading of loose refs, only for them to be freed immediately. Signed-off-by: Michael Haggerty <redacted> --- Fix a silly inefficiency from the lazy-loose changes. refs.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/refs.c b/refs.c
index d6bdb47..26c8fcd 100644
--- a/refs.c
+++ b/refs.c@@ -259,8 +259,13 @@ static void clear_ref_dir(struct ref_dir *dir); static void free_ref_entry(struct ref_entry *entry) { - if (entry->flag & REF_DIR) - clear_ref_dir(get_ref_dir(entry)); + if (entry->flag & REF_DIR) { + /* + * Do not use get_ref_dir() here, as that might + * trigger the reading of loose refs. + */ + clear_ref_dir(&entry->u.subdir); + } free(entry); }
--
1.7.10