From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible problems with kernel threading code?
Date: Fri, 20 Feb 2004 15:58:29 -0500 [thread overview]
Message-ID: <403674F5.2060902@nortelnetworks.com> (raw)
In-Reply-To: <40366344.9010109@redhat.com>
Ulrich Drepper wrote:
> Not that this is of any interest for this list but what the heck.
I thought that the kernel hangs might be of interest.
> The problem is your code.
>> int schedRc = pthread_setschedparam(t1, policy, &schedParam);
>
> There is no guarantee that t1 is filled before you it here in the newly
> created thread. Only when pthread_create() returns is the thread handle
> guaranteed to be written.
Ah, that explains the error. I'm still trying to track down the kernel
hangs though.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
prev parent reply other threads:[~2004-02-20 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 18:08 possible problems with kernel threading code? Chris Friesen
2004-02-20 19:43 ` Ulrich Drepper
2004-02-20 20:58 ` Chris Friesen [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=403674F5.2060902@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=drepper@redhat.com \
--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