Re: [Xenomai-core] rtdm_dev_register oops
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? :) If you leave the previous device registered on rmmod, oopses are programmed to occur: You leave references to unallocated memory behind. 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 signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] rtdm_dev_register oops
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 signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] rtdm_dev_register oops
Stefan Kisdaroczi wrote: 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, Then you have to find the bug that prevents proper deregistration. the rtdm registry is broken (cat /proc/xenomai/rtdm/names_devices hangs). That hanging of /proc output is fixed in a series of mine that is yet unmerged (as it is on hold, waiting for /proc infrastructure refactorings by Philippe). 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. If your filesystem hangs due to some bug of its own or in the underlying layers, you won't be able to touch any further file on that system as well. 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. Again, the problem is that the deregistration hangs. That needs to be understood and resolved. Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
