about summary refs log tree commit diff
path: root/elf/dl-load.c
diff options
context:
space:
mode:
authorManinder Singh <maninder1.s@samsung.com>2018-01-10 15:17:30 +0000
committerSzabolcs Nagy <szabolcs.nagy@arm.com>2021-04-06 14:44:09 +0100
commit395be7c2184645320c955b0ba214af9fa1ea9675 (patch)
treedd3d5623c2fbf20dcae590efcfdfa58c6f48dc34 /elf/dl-load.c
parent69499bb6eeb4f5d1b3502758208301d21042a783 (diff)
downloadglibc-395be7c2184645320c955b0ba214af9fa1ea9675.tar.gz
glibc-395be7c2184645320c955b0ba214af9fa1ea9675.tar.xz
glibc-395be7c2184645320c955b0ba214af9fa1ea9675.zip
elf: Fix data race in _dl_name_match_p [BZ #21349]
dlopen updates libname_list by writing to lastp->next, but concurrent
reads in _dl_name_match_p were not synchronized when it was called
without holding GL(dl_load_lock), which can happen during lazy symbol
resolution.

This patch fixes the race between _dl_name_match_p reading lastp->next
and add_name_to_object writing to it. This could cause segfault on
targets with weak memory order when lastp->next->name is read, which
was observed on an arm system. Fixes bug 21349.

(Code is from Maninder Singh, comments and description is from Szabolcs
Nagy.)

Co-authored-by: Vaneet Narang <v.narang@samsung.com>
Co-authored-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
Diffstat (limited to 'elf/dl-load.c')
-rw-r--r--elf/dl-load.c18
1 files changed, 17 insertions, 1 deletions
diff --git a/elf/dl-load.c b/elf/dl-load.c
index 2f760503c5..2832ab3540 100644
--- a/elf/dl-load.c
+++ b/elf/dl-load.c
@@ -438,7 +438,23 @@ add_name_to_object (struct link_map *l, const char *name)
   newname->name = memcpy (newname + 1, name, name_len);
   newname->next = NULL;
   newname->dont_free = 0;
-  lastp->next = newname;
+  /* CONCURRENCY NOTES:
+
+     Make sure the initialization of newname happens before its address is
+     read from the lastp->next store below.
+
+     GL(dl_load_lock) is held here (and by other writers, e.g. dlclose), so
+     readers of libname_list->next (e.g. _dl_check_caller or the reads above)
+     can use that for synchronization, however the read in _dl_name_match_p
+     may be executed without holding the lock during _dl_runtime_resolve
+     (i.e. lazy symbol resolution when a function of library l is called).
+
+     The release MO store below synchronizes with the acquire MO load in
+     _dl_name_match_p.  Other writes need to synchronize with that load too,
+     however those happen either early when the process is single threaded
+     (dl_main) or when the library is unloaded (dlclose) and the user has to
+     synchronize library calls with unloading.  */
+  atomic_store_release (&lastp->next, newname);
 }
 
 /* Standard search directories.  */