All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [FIX] Summary: Xenomai 2.3.2 and 2.4 lock-ups	and OOPSes
Date: Sun, 16 Sep 2007 21:31:27 +0200	[thread overview]
Message-ID: <1189971087.25006.210.camel@domain.hid> (raw)
In-Reply-To: <18157.27836.667782.514635@domain.hid>

On Sun, 2007-09-16 at 19:49 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
>  > 
>  > Please try this patch against v2.3.x. A double free issue on a task TCB
>  > already scheduled for memory release was causing all sorts of troubles,
>  > basically trashing the system heap afterwards:
> 
> Is not there anything similar needed for the posix skin ?
> 

pthread_create() does allocate the TCB itself, and properly releases it
upon error while creating the thread, so the syscall wrapper does not
have to free any TCB memory by itself, which is a prerequisite to enter
the double release situation. There is no possibility to run the
deletion hook indirectly on behalf of pthread_create() either, so I
think it's safe.

-- 
Philippe.




  reply	other threads:[~2007-09-16 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  9:27 [Xenomai-core] Summary: Xenomai 2.3.2 and 2.4 lock-ups and OOPSes Peter Soetens
2007-09-07 12:46 ` Philippe Gerum
2007-09-07 18:53   ` Gilles Chanteperdrix
2007-09-07 19:07     ` Gilles Chanteperdrix
2007-09-13  8:06   ` Peter Soetens
2007-09-13  8:22     ` Peter Soetens
2007-09-13 12:49     ` Philippe Gerum
2007-09-15 18:52 ` [Xenomai-core] [FIX] " Philippe Gerum
2007-09-16 17:49   ` Gilles Chanteperdrix
2007-09-16 19:31     ` Philippe Gerum [this message]
2007-09-17 12:55   ` Peter Soetens
2007-09-17 13:59   ` Peter Soetens

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=1189971087.25006.210.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@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.