From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Problem with pthread_setschedparam
Date: Thu, 10 May 2007 11:33:58 +0200 [thread overview]
Message-ID: <4642E706.7000500@domain.hid> (raw)
In-Reply-To: <1178789171.11688.142.camel@domain.hid>
Philippe Gerum wrote:
> On Thu, 2007-05-10 at 10:34 +0200, Gilles Chanteperdrix wrote:
>
>>>> >
>>>> > Ok, I could reproduce the problem. The issue is most likely an access to
>>>> > the thread memory after it has been freed which breaks the allocator
>>>> > linked list of free pages by replacing a link to a next free page by a
>>>> > NULL pointer. xnheap_alloc interprets this NULL pointer as the end of the
>>>> > linked list and hence considers that it is out of memory.
>>>>
>>>>And the winner is... RPI! The offset of the thread structure member that
>>>>is set to NULL is the one of the rpi pointer. Disabling RPI makes the
>>>>problem vanish.
>>>>
>>>>Philippe, when is this pointer set to NULL ?
>>>>
>>>
>>>When the thread leaves secondary mode or exits, which in turn removes it
>>>from the queue the nucleus considers for priority boosting the root
>>>thread. Check rpi_none().
>>
>>Conclusion: the problem is the one Andrew spotted, there are two
>>hooks and the shadow hook (which calls xnshadow_unmap, which in turn
>>calls rpi_pop, which sets the rpi pointer to null) gets called after the
>>other thread deletion hook which initially called xnfree, and now calls
>>xnfreesafe.
>>
>>But it seems that even xnfreesafe is not safe enough, and it frees the
>>thread pointer immediately whereas we would like the operation to be
>>deferred.
>>
>
>
> xnfreesafe was meant to prevent the caller from releasing some memory it
> could still rely on, e.g. stack space, by postponing the actual release
> until the idle thread is resumed. In your case, the problem is that it
> does not account for the primary/secondary mode of a shadow thread.
I am not so sure. I mean, even if the thread was deleted from the
context of another thread, the two hooks would be invoked and we would
need the free operation to be deferred until after the execution of the
second hook.
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2007-05-10 9:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51.1178704831.10156.xenomai@xenomai.org>
2007-05-09 12:49 ` [Xenomai-help] Problem with pthread_setschedparam Noren, Andrew
2007-05-09 13:32 ` Gilles Chanteperdrix
2007-05-09 13:43 ` Perrine Martignoni
2007-05-09 14:35 ` Perrine Martignoni
2007-05-09 20:37 ` Gilles Chanteperdrix
2007-05-09 21:23 ` Gilles Chanteperdrix
2007-05-09 22:02 ` Philippe Gerum
[not found] ` <17986.20728.617772.991566@domain.hid>
[not found] ` <1178784303.11688.108.camel@domain.hid>
2007-05-10 8:34 ` Gilles Chanteperdrix
2007-05-10 8:41 ` Gilles Chanteperdrix
2007-05-10 8:58 ` Daniel Schnell
2007-05-10 9:12 ` Gilles Chanteperdrix
2007-05-14 9:17 ` Daniel Schnell
2007-05-14 9:49 ` Wolfgang Grandegger
2007-05-14 9:56 ` Daniel Schnell
2007-05-18 9:58 ` Wolfgang Grandegger
2007-05-10 9:26 ` Philippe Gerum
2007-05-10 9:33 ` Gilles Chanteperdrix [this message]
2007-05-10 11:41 ` Perrine Martignoni
2007-05-10 12:06 ` Gilles Chanteperdrix
2007-05-10 12:47 ` Perrine Martignoni
2007-05-10 12:53 ` Gilles Chanteperdrix
2007-05-10 14:40 ` Philippe Gerum
2007-05-10 14:53 ` Gilles Chanteperdrix
2007-05-10 15:21 ` Philippe Gerum
2007-05-10 15:45 ` Gilles Chanteperdrix
2007-05-11 7:56 ` Perrine Martignoni
2007-05-11 8:17 ` Gilles Chanteperdrix
2007-05-11 8:24 ` Perrine Martignoni
2007-05-11 8:30 ` Perrine Martignoni
2007-05-11 8:50 ` Philippe Gerum
2007-05-09 8:55 Perrine Martignoni
2007-05-09 9:05 ` Gilles Chanteperdrix
2007-05-09 9:32 ` Gilles Chanteperdrix
2007-05-09 11:31 ` Perrine Martignoni
2007-05-09 12:34 ` Gilles Chanteperdrix
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=4642E706.7000500@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rpm@xenomai.org \
--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.