From: Henry Bausley <hbausley@domain.hid>
To: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] pthread_setschedparam: Resource temporarily unavailable
Date: Tue, 18 Aug 2009 08:29:35 -0700 [thread overview]
Message-ID: <1250609375.19848.8.camel@domain.hid> (raw)
In-Reply-To: <4A89DDE8.2010907@domain.hid>
Thank you the memory leak is gone.
On Tue, 2009-08-18 at 00:47 +0200, Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
> > Henry Bausley wrote:
> >> I used the defaults that came up for my 2.6.28.8 kernel I-pipe 2.4-05.
> >> I'll rebuild the kernel with 2.6
> >
> > Ok. Forget it, I can reproduce it. I simply forgot to enable Xenomai
> > posix skin shared memories in the kernel configuration. The bug does not
> > happen on head though, only on 2.4. And this with the same version of
> > the I-pipe.
>
> It should be fixed in the repository. Here is the patch:
>
> diff --git a/ksrc/skins/posix/syscall.c b/ksrc/skins/posix/syscall.c
> index ec0c102..898cc91 100644
> --- a/ksrc/skins/posix/syscall.c
> +++ b/ksrc/skins/posix/syscall.c
> @@ -2717,6 +2717,8 @@ static int __munmap_epilogue(struct pt_regs *regs)
> xnlock_put_irqrestore(&pse51_assoc_lock, s);
>
> err = munmap(umap->kaddr, len);
> + if (!err)
> + xnfree(umap);
>
> return !err ? 0 : -thread_get_errno();
> }
>
>
**********************************************************
Outbound scan for Spam or Virus by Barracuda at Delta Tau
**********************************************************
prev parent reply other threads:[~2009-08-18 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 18:02 [Xenomai-help] pthread_setschedparam: Resource temporarily unavailable Henry Bausley
2009-08-13 18:33 ` Gilles Chanteperdrix
2009-08-16 23:07 ` Henry Bausley
[not found] ` <1250200537.28789.8.camel@domain.hid>
[not found] ` <4A8808BA.4080504@domain.hid>
2009-08-17 21:17 ` Henry Bausley
2009-08-17 22:12 ` Gilles Chanteperdrix
2009-08-17 22:47 ` Gilles Chanteperdrix
2009-08-18 15:29 ` Henry Bausley [this message]
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=1250609375.19848.8.camel@domain.hid \
--to=hbausley@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.