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@

1 files changed, 6 insertions, 0 deletions

diff --git a/src/regress/lib/libc/stdio_threading/flockfile/Makefile b/src/regress/lib/libc/stdio_threading/flockfile/Makefile
new file mode 100644
index 0000000000..171ccc7ac7
--- /dev/null
+++ b/src/regress/lib/libc/stdio_threading/flockfile/Makefile
@@ -0,0 +1,6 @@
+TOPDIR=${.CURDIR}
+PROG=flockfile_test
+CFLAGS+=-I${TOPDIR}/../include/
+LDFLAGS+=-lpthread
+
+.include <bsd.regress.mk>