From: Pavel Emelyanov <xemul@openvz.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Duncan Sands <baldrick.bulk@free.fr>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][USBATM]: convert heavy init dances to kthread API
Date: Thu, 07 Feb 2008 19:37:24 +0300 [thread overview]
Message-ID: <47AB33C4.7060501@openvz.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802071116360.4128-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 7 Feb 2008, Pavel Emelyanov wrote:
>
>>> Does the kthread API guarantee that the kthread is not running until you call
>> It does. That's why the race, you mentioned above is impossible.
>
> That is wrong. The API guarantees only that the kthread is initially
> created in a non-running state. It cannot guarantee that no other
> task will wake up the kthread before the caller does.
Other tasks cannot wake this thread up since they do not
know the struct task_struct pointer.
> Alan Stern
>
>
next prev parent reply other threads:[~2008-02-07 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 16:15 [PATCH][USBATM]: convert heavy init dances to kthread API Pavel Emelyanov
2008-02-06 17:20 ` Duncan Sands
2008-02-07 9:23 ` Pavel Emelyanov
2008-02-07 9:57 ` Duncan Sands
2008-02-07 10:08 ` Pavel Emelyanov
2008-02-10 20:30 ` Duncan Sands
2008-02-11 11:22 ` Pavel Emelyanov
2008-02-11 11:51 ` Duncan Sands
2008-02-07 16:18 ` Alan Stern
2008-02-07 16:37 ` Pavel Emelyanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 12:26 [PATCH] Usbatm: " Pavel Emelyanov
2008-02-11 12:39 ` Duncan Sands
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=47AB33C4.7060501@openvz.org \
--to=xemul@openvz.org \
--cc=baldrick.bulk@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.