linux-kernel - Possible 2.6.24-rc7 issue w/respect to pthreads

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <39848.76.189.45.79.1199874932.squirrel@webmail.kavaga.com>
Date:	Wed, 9 Jan 2008 02:35:32 -0800 (PST)
From:	tom@...aga.com
To:	linux-kernel@...r.kernel.org
Subject: Possible 2.6.24-rc7 issue w/respect to pthreads

To Whom It May Concern,

After I patched my 2.6.23 kernel to 2.6.24-rc7 this morning, I noticed
some odd behavior with respect to POSIX threads in a test program I had
written (originally to test epoll.)

The behavior is as follows:

1.  main() creates a new thread of execution with pthread_create
2.  thread_func() immediately calls pthread_detach(), which is supposed to
ensure that thread resources are cleaned up when the thread terminates.
3.  The spawned thread sleeps and then prints a message "got here"
4.  The main thread calls pthread_join().  According to the POSIX
documentation, this should suspend execution until the spawned thread has
terminated.

What I'm seeing is that the main thread terminates immediately.  If I
comment out the call to pthread_detach(), the program runs normally.  If I
boot with my 2.6.23 kernel, the program runs normally.

I'm not sure if this is some oversight on my part but similar programs
operate correctly on my Debian etch installation with 2.6.18 as well as
with the newer 23 kernel, but not with the patch.

If you have any questions, don't hesitate to email me; my address is
provided below.

See Attached (bug.c)

Tom R. Dial
tom@...aga.com
View attachment "bug.c" of type "text/x-csrc" (1541 bytes)