From 28d8cf0bbfe2d8e27749a1453bd2771c8e41c31b Mon Sep 17 00:00:00 2001 From: guenther <> Date: Mon, 19 Jan 2026 23:01:00 +0000 Subject: 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@ --- src/regress/lib/libc/stdio_threading/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/regress/lib/libc/stdio_threading/Makefile') diff --git a/src/regress/lib/libc/stdio_threading/Makefile b/src/regress/lib/libc/stdio_threading/Makefile index e42481afc2..5823b6e284 100644 --- a/src/regress/lib/libc/stdio_threading/Makefile +++ b/src/regress/lib/libc/stdio_threading/Makefile @@ -1,3 +1,3 @@ -SUBDIR += fopen fread fwrite fgetln fgets fputs +SUBDIR += fopen fread fwrite fgetln fgets fputs flockfile .include -- cgit v1.2.3-55-g6feb