From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Native: Fixing auto-cleanup
Date: Fri, 16 Oct 2009 19:14:42 +0200 [thread overview]
Message-ID: <4AD8AA02.1050309@domain.hid> (raw)
In-Reply-To: <4AD8A87C.4040706@domain.hid>
Jan Kiszka wrote:
> Hi,
>
> our automatic object cleanup on process termination is "slightly" broken
> for the native skin. The inline and macro magic behind
> __native_*_flush_rq() blindly calls rt_*_delete(), but that's not
> correct for mutexes (we can leak memory and/or corrupt the system heap),
Hmm, xnheap_free is actually robust enough to cope with this invalid
release (sem_heap object to system heap), so no corruptions. Still, we
leak, and that's what made me stumble over these bugs.
> queues and heaps (we may leak shared heaps).
>
> I'm in the process of fixing this, but that latter two are tricky. They
> need user space information (the user space address of the mapping base)
> for ordinary cleanup, and this is not available otherwise.
>
> At the time we are called with our cleanup handler, can we assume that
> the dying process has already unmapped all its rtheap segments? In that
> case I could simply pass NULL as base address, and the deletion will
> succeed. If not, I would currently lack a good idea how to resolve this
> issue.
>
> Jan
>
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-10-16 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 17:08 [Xenomai-core] Native: Fixing auto-cleanup Jan Kiszka
2009-10-16 17:14 ` Jan Kiszka [this message]
2009-10-17 17:15 ` Philippe Gerum
2009-10-18 12:54 ` Jan Kiszka
2009-10-18 16:48 ` Philippe Gerum
2009-10-18 17:56 ` Jan Kiszka
2009-10-20 10:00 ` Philippe Gerum
2009-10-20 10:29 ` Jan Kiszka
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=4AD8AA02.1050309@domain.hid \
--to=jan.kiszka@domain.hid \
--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.