From: Ulrich Drepper <drepper@redhat.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible problems with kernel threading code?
Date: Fri, 20 Feb 2004 11:43:00 -0800 [thread overview]
Message-ID: <40366344.9010109@redhat.com> (raw)
In-Reply-To: <40364D01.9030504@nortelnetworks.com>
Not that this is of any interest for this list but what the heck.
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.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2004-02-20 20:01 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 [this message]
2004-02-20 20:58 ` Chris Friesen
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=40366344.9010109@redhat.com \
--to=drepper@redhat.com \
--cc=cfriesen@nortelnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.