Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
Gilles Chanteperdrix wrote: Gilles Chanteperdrix wrote: misinterpretation. When issuing syscalls with a fixed muxid whereas there is no interface corresponding to this muxid, the nucleus crashes, but it is acceptable, user-space interfaces should issue an __xn_sys_bind syscall first. This is not even possible, since the invalid syscall go through do_hisyscall_event first and get handled there. Do I get this correctly now: problem fixed by commit #1264? Is there still anything we should do about the RTDM lib? Jan signature.asc Description: OpenPGP digital signature ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
Jan Kiszka wrote: Jan Kiszka wrote: Hi, wondering why suddenly things crash on invoking the latency test, I realised that I turned the nucleus into a module which was not yet loaded. Here is the oops in this case: Correction: the nucleus was still compiled in, the native skin was missing. After a more thorough inspection, the problem was the xnshadow_p() call at the very end of do_losyscall_event. When no pod is loaded this call oopses. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
Jan Kiszka wrote: Jan Kiszka wrote: Hi, wondering why suddenly things crash on invoking the latency test, I realised that I turned the nucleus into a module which was not yet loaded. Here is the oops in this case: Correction: the nucleus was still compiled in, the native skin was missing. After a few investigation, the problem appears to be that the nucleus assume that user-space skins will issue a bind syscall before using a skin, and that the user-space RTDM library does not exit if binding fails. So, there are two ways we can fix this problem: - either we make the nucleus paranoid and have it handle gracefully syscalls to non loaded tables; - or we make the user-space RTDM library behave like other skins and exit if the interface is not bound. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
On Fri, 2006-06-23 at 15:41 +0200, Gilles Chanteperdrix wrote: Jan Kiszka wrote: Jan Kiszka wrote: Hi, wondering why suddenly things crash on invoking the latency test, I realised that I turned the nucleus into a module which was not yet loaded. Here is the oops in this case: Correction: the nucleus was still compiled in, the native skin was missing. After a few investigation, the problem appears to be that the nucleus assume that user-space skins will issue a bind syscall before using a skin, and that the user-space RTDM library does not exit if binding fails. I don't get it: the muxid should be invalid then(?) So, there are two ways we can fix this problem: - either we make the nucleus paranoid and have it handle gracefully syscalls to non loaded tables; - or we make the user-space RTDM library behave like other skins and exit if the interface is not bound. -- Philippe. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
Philippe Gerum wrote: On Fri, 2006-06-23 at 15:41 +0200, Gilles Chanteperdrix wrote: Jan Kiszka wrote: Jan Kiszka wrote: Hi, wondering why suddenly things crash on invoking the latency test, I realised that I turned the nucleus into a module which was not yet loaded. Here is the oops in this case: Correction: the nucleus was still compiled in, the native skin was missing. After a few investigation, the problem appears to be that the nucleus assume that user-space skins will issue a bind syscall before using a skin, and that the user-space RTDM library does not exit if binding fails. I don't get it: the muxid should be invalid then(?) Yes the muxid is -1 and everything works fine, it was just a misinterpretation. When issuing syscalls with a fixed muxid whereas there is no interface corresponding to this muxid, the nucleus crashes, but it is acceptable, user-space interfaces should issue an __xn_sys_bind syscall first. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
