Re: [Xenomai-core] rt_sem_create bug when registring in proc

2008-09-28 Thread stephane ancelot
Le Sun, 28 Sep 2008 16:25:56 +0200, Philippe Gerum <[EMAIL PROTECTED]> a  
écrit:

> stephane ancelot wrote:
>> Hi,
>> I have the following kernel bug, when using a string name in
>> rt_sem_create. using NULL as name do not report this problem.
>>
>> BUG: unable to handle kernel paging request at virtual address de82a268
>> printing eip: c025d51a *pde = 1dd3e067 *pte = 
>> Oops:  [#1] PREEMPT
>> Modules linked in: xx(P) elok_s(P) e100 mii
>>
>
> You did not specify the Xenomai version in use. Looking at this output,  
> you may
> want to search the bug in your proprietary module code first; it seems  
> that you
> passed a string laid into the data segment of a module that has been  
> unloaded,
> without removing the semaphore it had initially created.
>

Hi,

You are right, the semaphore was created in a thread meanwhile a bad coded  
init module was unloading it. (return missing in init routine ) thanks.
Best Regards
Steph




>> Pid: 4, comm: events/0 Tainted: P(2.6.24.2-ipipe #3)
>> EIP: 0060:[] EFLAGS: 00010246 CPU: 0
>> EIP is at strlen+0xa/0x20
>> EAX:  EBX: 8124 ECX:  EDX: de82a268
>> ESI: de82a268 EDI: de82a268 EBP: 0001 ESP: ddc27e8c
>>   DS: 007b ES: 007b FS:  GS:  SS: 0068
>> Process events/0 (pid: 4, ti=ddc26000 task=ddc19ab0 task.ti=ddc26000)<0>
>> I-pipe domain Linux
>> Stack: ddc27ebc c01e445b dde783c0 c0257d2a dde78140 de82a268 de82a268
>> c016e7a0
>> c048aebc  c01e46d4 0001 dde78140 c04fbac4 c016338c
>> 0200
>>    007b 0002  dde783c0
>> dde78140
>> Call Trace:
>>   [] proc_create+0x4b/0x110
>>   [] idr_get_new+0xa/0x30
>>   [] __sem_read_proc+0x0/0x130
>>   [] create_proc_entry+0x44/0x90
>>   [] registry_proc_callback+0xa1c/0xb00
>>   [] update_curr+0x71/0x100
>>   [] update_curr+0xf8/0x100
>>   [] set_next_entity+0x1f/0x50
>>   [] registry_proc_callback+0x0/0xb00
>>   [] run_workqueue+0xb6/0x1a0
>>   [] schedule+0x1df/0x3d0
>>   [] worker_thread+0x6d/0xa0
>>   [] autoremove_wake_function+0x0/0x50
>>   [] worker_thread+0x0/0xa0
>>   [] kthread+0x42/0x70
>>   [] kthread+0x0/0x70
>>   [] kernel_thread_helper+0x7/0x1c
>>   ===
>> Code: 00 56 89 c6 89 d0 88 c4 ac 38 e0 74 09 84 c0 75 f7 be 01 00 00 00  
>> 89
>> f0 48 5e c3 8d b6 00 00 00 00 57 b9 ff ff ff ff 89 c7 31 c0  ae f7  
>> d1
>> 49 5f 89 c8 c3 8d b6 00 00 00 00 8d bc 27 00 00 00
>> EIP: [] strlen+0xa/0x20 SS:ESP 0068:ddc27e8c
>> ---[ end trace 614a6309c2874abe ]---
>>
>> Best regards
>> S.Ancelot
>>
>> ___
>> Xenomai-core mailing list
>> Xenomai-core@gna.org
>> https://mail.gna.org/listinfo/xenomai-core
>>
>
>



___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core


Re: [Xenomai-core] rt_sem_create bug when registring in proc

2008-09-28 Thread Philippe Gerum
stephane ancelot wrote:
> Hi,
> I have the following kernel bug, when using a string name in  
> rt_sem_create. using NULL as name do not report this problem.
> 
> BUG: unable to handle kernel paging request at virtual address de82a268
> printing eip: c025d51a *pde = 1dd3e067 *pte = 
> Oops:  [#1] PREEMPT
> Modules linked in: xx(P) elok_s(P) e100 mii
>

You did not specify the Xenomai version in use. Looking at this output, you may
want to search the bug in your proprietary module code first; it seems that you
passed a string laid into the data segment of a module that has been unloaded,
without removing the semaphore it had initially created.

> Pid: 4, comm: events/0 Tainted: P(2.6.24.2-ipipe #3)
> EIP: 0060:[] EFLAGS: 00010246 CPU: 0
> EIP is at strlen+0xa/0x20
> EAX:  EBX: 8124 ECX:  EDX: de82a268
> ESI: de82a268 EDI: de82a268 EBP: 0001 ESP: ddc27e8c
>   DS: 007b ES: 007b FS:  GS:  SS: 0068
> Process events/0 (pid: 4, ti=ddc26000 task=ddc19ab0 task.ti=ddc26000)<0>
> I-pipe domain Linux
> Stack: ddc27ebc c01e445b dde783c0 c0257d2a dde78140 de82a268 de82a268  
> c016e7a0
> c048aebc  c01e46d4 0001 dde78140 c04fbac4 c016338c  
> 0200
>    007b 0002  dde783c0  
> dde78140
> Call Trace:
>   [] proc_create+0x4b/0x110
>   [] idr_get_new+0xa/0x30
>   [] __sem_read_proc+0x0/0x130
>   [] create_proc_entry+0x44/0x90
>   [] registry_proc_callback+0xa1c/0xb00
>   [] update_curr+0x71/0x100
>   [] update_curr+0xf8/0x100
>   [] set_next_entity+0x1f/0x50
>   [] registry_proc_callback+0x0/0xb00
>   [] run_workqueue+0xb6/0x1a0
>   [] schedule+0x1df/0x3d0
>   [] worker_thread+0x6d/0xa0
>   [] autoremove_wake_function+0x0/0x50
>   [] worker_thread+0x0/0xa0
>   [] kthread+0x42/0x70
>   [] kthread+0x0/0x70
>   [] kernel_thread_helper+0x7/0x1c
>   ===
> Code: 00 56 89 c6 89 d0 88 c4 ac 38 e0 74 09 84 c0 75 f7 be 01 00 00 00 89  
> f0 48 5e c3 8d b6 00 00 00 00 57 b9 ff ff ff ff 89 c7 31 c0  ae f7 d1  
> 49 5f 89 c8 c3 8d b6 00 00 00 00 8d bc 27 00 00 00
> EIP: [] strlen+0xa/0x20 SS:ESP 0068:ddc27e8c
> ---[ end trace 614a6309c2874abe ]---
> 
> Best regards
> S.Ancelot
> 
> ___
> Xenomai-core mailing list
> Xenomai-core@gna.org
> https://mail.gna.org/listinfo/xenomai-core
> 


-- 
Philippe.

___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core