All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steven Kauffmann <steven.kauffmann@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Kernel Oops calling rt_dev_close
Date: Tue, 02 Sep 2008 14:29:55 +0200	[thread overview]
Message-ID: <48BD31C3.2030104@domain.hid> (raw)
In-Reply-To: <ff1d78710809020518o6bc21376k6d06544754b85aa@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Steven Kauffmann wrote:
> On Tue, Sep 2, 2008 at 12:22 PM, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>> Steven Kauffmann wrote:
>>> Hi all,
>>>
>>> I'm getting Kernel oops when calling rt_dev_close in my application
>>> [*]. The application creates a new real-time task and in this task
>>> rt_dev_recvfrom is waiting for incoming CAN messages.
>>>
>>> In the close function of the application I first call rt_dev_close and
>>> after that I kill the thread with rt_task_delete. I also wait for the
>>> termination of this thread with rt_task_join. But when rt_dev_close is
>>> called, the kernel oops occurs.
>> Do you have a (small) test case for this issue? Does it work with a
>> virtual CAN device as well? That would be the fastest way to track down
>> the issue.
> 
> The test case (see attached file) reproduces the kernel oops.

So it's socket closing while some other tasks blocks in recv.

> 
> The kernel oops also occurs when using the virtual CAN device.

Great, will look into this later today.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2008-09-02 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  9:50 [Xenomai-help] Kernel Oops calling rt_dev_close Steven Kauffmann
2008-09-02 10:22 ` Jan Kiszka
2008-09-02 12:18   ` Steven Kauffmann
2008-09-02 12:29     ` Jan Kiszka [this message]
2008-09-03  6:14     ` Jan Kiszka

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=48BD31C3.2030104@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=steven.kauffmann@domain.hid \
    --cc=xenomai@xenomai.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.