diff options
| author | guenther <> | 2026-01-19 23:01:00 +0000 |
|---|---|---|
| committer | guenther <> | 2026-01-19 23:01:00 +0000 |
| commit | 28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b (patch) | |
| tree | 70a6f669625e0a3bd8d7ad550c55357341c846f0 /src/lib/libc/stdlib/mktemp.c | |
| parent | 72cdd91797afb2b9796ee9f67324a53c5fc6effe (diff) | |
| download | openbsd-28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b.tar.gz openbsd-28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b.tar.bz2 openbsd-28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b.zip | |
While almost all the libc locks are taken and released in the same
libc call, flockfile() and ftrylockfile() can be called when
single-threaded and then--while 'holding' the lock--the process can
create another thread, resulting in a broken state. Have the
f{lock,trylock,unlock}file() APIs *always* do real locking so the
exposed state is always consistent.
ok dlg@
Diffstat (limited to 'src/lib/libc/stdlib/mktemp.c')
0 files changed, 0 insertions, 0 deletions