All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Krzysztof Błaszkowski" <kb@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] xenomai 2.5.3/native, kernel 2.6.31.8 and fork()
Date: Tue, 17 Aug 2010 16:41:07 +0200	[thread overview]
Message-ID: <1282056067.1730.245.camel@domain.hid> (raw)
In-Reply-To: <1282047938.5255.89.camel@domain.hid>

On Tue, 2010-08-17 at 14:25 +0200, Krzysztof Błaszkowski wrote:
> Hello,
> 
> I found recently that large application uses to segfault before fork()
> leaves its glibc wrapper.
> 
> I included here a test suite which can be easily used to verify what
> goes wrong. It may be necessary to adjust makefile to compile the code.
> So, the console is missing output from line #89. We can see instead a
> message that getpid couldn't be linked which is 1st sign of memory
> corruption.
> 
> i used to think that this issue could be related to not unbinding heap
> before fork() but it turned out that it is enough to link userspace with
> xenomai libraries.
> 
> I wonder if this is known issue and if there is any fix, does 2.5.4 work
> same ? or maybe there is something wrong with the kernel i use (or adeos
> patch)
> 
> Another question is why rt_task_create() is marked deprecated in native
> skin.

rt_task_create() as defined by the kernel-side API is marked as
deprecated. The user-space version of rt_task_create() is not.

>  Does it mean that native skin is going to be removed from source
> tree ?
> 

No. It means that starting with the next major evolution of Xenomai
(i.e. 3.x), skins will no more export any kernel-based API (except
RTDM). In short, if your application is running in user-space, nothing
will change for you. OTOH, applications currently running in kernel
space over the native API should consider moving to user-space at some
point, because we won't support the former programming model
indefinitely. The rationale for this decision is explained here:
http://www.xenomai.org/index.php/Xenomai:Roadmap#What_Will_Change_With_Xenomai_3

The keyword here is "application", obviously not drivers, which are by
essence better supported in kernel space in the Linux environment, and
Xenomai 3.x will keep on providing what is required to develop them
there over RTDM.

> Regards,
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core

-- 
Philippe.




  parent reply	other threads:[~2010-08-17 14:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 12:25 [Xenomai-core] xenomai 2.5.3/native, kernel 2.6.31.8 and fork() Krzysztof Błaszkowski
2010-08-17 12:33 ` Gilles Chanteperdrix
2010-08-17 12:34   ` Krzysztof Błaszkowski
2010-08-17 12:40     ` Gilles Chanteperdrix
2010-08-17 12:54       ` Krzysztof Błaszkowski
2010-08-17 13:06         ` Gilles Chanteperdrix
2010-08-17 13:19           ` Krzysztof Błaszkowski
2010-08-17 13:27             ` Gilles Chanteperdrix
2010-08-17 13:57               ` Krzysztof Błaszkowski
2010-08-17 14:08                 ` Gilles Chanteperdrix
2010-08-17 14:12                   ` Krzysztof Błaszkowski
2010-08-17 14:17                     ` Gilles Chanteperdrix
2010-08-17 16:07                       ` Krzysztof Błaszkowski
2010-08-17 12:35   ` Krzysztof Błaszkowski
2010-08-17 12:40     ` Gilles Chanteperdrix
2010-08-17 14:41 ` Philippe Gerum [this message]
2010-08-17 16:09   ` Krzysztof Błaszkowski
2010-08-17 22:59 ` Gilles Chanteperdrix
2010-08-18 10:22   ` Krzysztof Błaszkowski
2010-08-18 11:00     ` Gilles Chanteperdrix
2010-08-18 11:40       ` Krzysztof Błaszkowski
2010-08-18 12:00         ` Gilles Chanteperdrix
2010-08-18 12:17           ` Krzysztof Błaszkowski
2010-08-18 12:37             ` Gilles Chanteperdrix
2010-08-18 12:55               ` Krzysztof Błaszkowski
2010-08-18 13:39                 ` Gilles Chanteperdrix
2010-08-18 14:04                   ` Krzysztof Błaszkowski
2010-08-18 14:10                     ` Gilles Chanteperdrix
2010-08-18 14:25                       ` Krzysztof Błaszkowski
2010-08-18 14:30                         ` Gilles Chanteperdrix
2010-08-18 15:09                           ` Krzysztof Błaszkowski
2010-08-18 15:13                             ` Gilles Chanteperdrix
2010-08-18 15:16                               ` Krzysztof Błaszkowski
2010-08-18 15:43                                 ` Gilles Chanteperdrix
2010-08-18 16:30                                   ` Krzysztof Błaszkowski
2010-08-18 16:51                                   ` Krzysztof Błaszkowski
2010-08-18 17:17                                   ` Krzysztof Błaszkowski
2010-08-20  9:47                               ` Krzysztof Błaszkowski
2010-08-20  9:54                                 ` Gilles Chanteperdrix
2010-08-20 15:50                                   ` Krzysztof Błaszkowski
2010-08-21 17:06                                     ` Gilles Chanteperdrix
2010-08-21 17:36                                       ` Gilles Chanteperdrix
2010-08-22 15:13                                         ` Philippe Gerum
2010-08-22 23:34                                           ` Gilles Chanteperdrix
2010-08-18 15:13                           ` Krzysztof Błaszkowski
2010-08-18 11:05     ` 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=1282056067.1730.245.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=kb@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.