about summary refs log tree commit diff
path: root/src/linux/sync_file_range.c
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2019-02-16 09:13:45 -0500
committerRich Felker <dalias@aerifal.cx>2019-02-16 10:11:22 -0500
commite4235d70672d9751d7718ddc2b52d0b426430768 (patch)
treecf4d965f2a440b641adca6fd3ddf5f17278e3210 /src/linux/sync_file_range.c
parent8f11e6127fe93093f81a52b15bb1537edc3fc8af (diff)
downloadmusl-e4235d70672d9751d7718ddc2b52d0b426430768.tar.gz
musl-e4235d70672d9751d7718ddc2b52d0b426430768.tar.xz
musl-e4235d70672d9751d7718ddc2b52d0b426430768.zip
rewrite __synccall in terms of global thread list
the __synccall mechanism provides stop-the-world synchronous execution
of a callback in all threads of the process. it is used to implement
multi-threaded setuid/setgid operations, since Linux lacks them at the
kernel level, and for some other less-critical purposes.

this change eliminates dependency on /proc/self/task to determine the
set of live threads, which in addition to being an unwanted dependency
and a potential point of resource-exhaustion failure, turned out to be
inaccurate. test cases provided by Alexey Izbyshev showed that it
could fail to reflect newly created threads. due to how the
presignaling phase worked, this usually yielded a deadlock if hit, but
in the worst case it could also result in threads being silently
missed (allowed to continue running without executing the callback).
Diffstat (limited to 'src/linux/sync_file_range.c')
0 files changed, 0 insertions, 0 deletions