<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/regress/lib/libc/stdio_threading/flockfile/Makefile, branch master</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=master</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2026-01-19T23:01:00+00:00</updated>
<entry>
<title>While almost all the libc locks are taken and released in the same</title>
<updated>2026-01-19T23:01:00+00:00</updated>
<author>
<name>guenther</name>
<email></email>
</author>
<published>2026-01-19T23:01:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b'/>
<id>urn:sha1:28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b</id>
<content type='text'>
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@
</content>
</entry>
</feed>
