From: "Daniel Krüger" <daniel.krueger@systec-electronic.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel_thread() usage found in staging
Date: Wed, 18 Mar 2009 14:30:40 +0100 [thread overview]
Message-ID: <49C0F780.2020904@systec-electronic.com> (raw)
Hello,
sorry for stepping in. I found the original posting via Google while
trying to compile the openPOWERLINK protocol stack with a recent Linux
kernel. I am the official maintainer of openPOWERLINK.
> ./epl/ShbIpc-LinuxKernel.c:
> kernel_thread(ShbIpcThreadSignalNewData, pShbInstance_p,
> kernel_thread(ShbIpcThreadSignalJobReady, pShbInstance_p,
>
> ./epl/EplSdoUdpu.c:
> kernel_thread(EplSdoUdpThread, &SdoUdpInstance_g, CLONE_KERNEL);
As I understand, there are some issues (race conditions) with the
kthread-API and signals. I need signals, because the kernel-threads may
block in some I/O functions.
What is the right way to use the kthread-API with signals? Or are there
any solutions to avoid signals?
Is there any sample code that shows how to do it?
Thanks in advance for any help.
Regards,
Daniel Krüger
--
SYS TEC electronic GmbH
August-Bebel-Str. 29
D-07973 Greiz
Telefon : +49 (0) 3661 6279 0
Fax : +49 (0) 3661 6279 99
Email : daniel.krueger@systec-electronic.com
Internet : http://www.systec-electronic.com
Managing Director : Dipl.-Phys. Siegmar Schmidt
Commercial registry : Amtsgericht Jena, HRB 205563
next reply other threads:[~2009-03-18 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 13:30 Daniel Krüger [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-13 8:26 kernel_thread() usage found in staging Peter Teoh
2009-03-13 21:24 ` Greg KH
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=49C0F780.2020904@systec-electronic.com \
--to=daniel.krueger@systec-electronic.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