public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallón" <jamagallon@ono.com>
To: Andrew Morton <akpm@osdl.org>,
	"Linux-Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: Problem with POSIX threads in latest kernel...
Date: Mon, 22 Jan 2007 23:59:41 +0100	[thread overview]
Message-ID: <20070122235941.52b1b228@werewolf-wl> (raw)
In-Reply-To: <20070122115630.a3d790f5.akpm@osdl.org>

On Mon, 22 Jan 2007 11:56:30 -0800, Andrew Morton <akpm@osdl.org> wrote:

> > On Tue, 16 Jan 2007 02:47:10 +0100 "J.A. Magallón" <jamagallon@ono.com> wrote:
> > Hi...
> > 
> > I run the (almost) latest -mm kernel (2.6.20-rc3-mm1), and see some strange behaviour
> > with POSIX threads (glibc-2.4).
> > I have downgraded my test to a simple textboox example for a SMP-safe spool
> > queue, it's just a circular queue with a mutex and a condition variable for in
> > and out. I have seen the same structure in several places.
> > 
> > Well, it just sometimes gets blocked. GDB says its stuck in pthread_wait().
> > I could swear it worked on previous kernels. It works as is on IRIX.
> > I will try to build an older kernel to test.
> > I takes a second to block it with something like while :; tst; done.
> > 
> > Any ideas ?
> 
> Do I need to worry about this still?

Oops, no, sorry. It was buggy code that previously seemed to work.
Buggy code:

	pthread_mutex_lock(&slots_mutex);
		while (slots<=0)
			pthread_cond_wait(&slots_cond,&slots_mutex);
		slots--;
		items++;
	pthread_mutex_unlock(&slots_mutex);

	pthread_mutex_lock(&items_mutex);
		pthread_cond_signal(&items_cond);
	pthread_mutex_unlock(&items_mutex);

(buggy because it acceses items without locking. The same in the other
endpoint of the queue).

Correct code:

	pthread_mutex_lock(&slots_mutex);
		while (slots<=0)
			pthread_cond_wait(&slots_cond,&slots_mutex);
		slots--;
	pthread_mutex_unlock(&slots_mutex);

	pthread_mutex_lock(&items_mutex);
		items++;
		pthread_cond_signal(&items_cond);
	pthread_mutex_unlock(&items_mutex);

So don't worry. I was so busy I forgot to post the solution.

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.19-jam04 (gcc 4.1.2 20061110 (prerelease) (4.1.2-0.20061110.2mdv2007.1)) #0 SMP PREEMPT

      parent reply	other threads:[~2007-01-22 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16  1:47 Problem with POSIX threads in latest kernel J.A. Magallón
     [not found] ` <20070122115630.a3d790f5.akpm@osdl.org>
2007-01-22 22:59   ` J.A. Magallón [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070122235941.52b1b228@werewolf-wl \
    --to=jamagallon@ono.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox