From: Stefan Kisdaroczi <kisda@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] rtdm_dev_register oops
Date: Tue, 18 May 2010 15:42:27 +0200 [thread overview]
Message-ID: <4BF29943.3010309@domain.hid> (raw)
In-Reply-To: <4BF273ED.2070802@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Am 18.05.2010 13:03, schrieb Jan Kiszka:
> Stefan Kisdaroczi wrote:
>> hi,
>>
>> i got a exception in rtdm_dev_register(). I didnt call rtdm_dev_unregister in my driver
>> and after insmodding the module again I got a oops.
>
> And that is surprising to you? :)
A bit.
> If you leave the previous device registered on rmmod, oopses are
> programmed to occur: You leave references to unallocated memory behind.
If one device fails to unregister i can't register any other device anymore,
the rtdm registry is broken (cat /proc/xenomai/rtdm/names_devices hangs).
That was surprising. If I have one corrupt file on my disk i can still
create/access other files or list the filenames without exception.
Please don't get me wrong, but its not obvious for me that a registry
behaves like that, but i can life with it. Sorry for the noise.
Stefan
> Jan
>
>> xenomai 2.5.3, linux 2.6.32.11, x86 32bit, ubuntu 10.04.
>>
>> Attached is the dmesg-trace and a small rtdm-module foo.c for reproduction:
>> insmod ./xeno_foo.ko
>> rmmod xeno_foo
>> insmod ./xeno_foo.ko -> oops
>>
>> thanks
>> stefan
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2010-05-18 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 10:15 [Xenomai-core] rtdm_dev_register oops Stefan Kisdaroczi
2010-05-18 11:03 ` Jan Kiszka
2010-05-18 13:42 ` Stefan Kisdaroczi [this message]
2010-05-18 16:43 ` 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=4BF29943.3010309@domain.hid \
--to=kisda@domain.hid \
--cc=jan.kiszka@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.