From: John Morris <john@zultron.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] 3.5.7 posix/mprotect fixed; (Was: posix/mprotect failure)
Date: Tue, 15 Jan 2013 01:16:46 -0600 [thread overview]
Message-ID: <50F5025E.1040500@zultron.com> (raw)
In-Reply-To: <50F48CBB.7080605@xenomai.org>
On 01/14/2013 04:54 PM, Gilles Chanteperdrix wrote:
> On 01/14/2013 09:52 PM, John Morris wrote:
>> http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-gdb-posix-mprotect-3.5.7-test.log
>
>
> So, you are compiling with _FORTIFY_SOURCE, that is the difference with
> how we are compiling. Is it easy for you to set _FORTIFY_SOURCE to 0?
Wow, you picked that out instantly. That fixes it. RH-like distros
define _FORTIFY_SOURCE in the default CFLAGS, worthy of a wiki note:
http://fedoraproject.org/wiki/Security/Features#Compile_Time_Buffer_Checks_.28FORTIFY_SOURCE.29
I'm guessing that Xenomai-enabled applications won't have to worry about
this, because they'll only be compiling header files. Is that about
right, or should there be a notice in the -devel package?
Here's the latest xeno-regression-test run:
http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-xeno-regression-test-3.5.7-test.log
The latest xeno-regression-test run still has a few small problems:
1) "xddp_test" fails: "...IPCPROTO_XDDP): Address family not supported
by protocol". DRIVERS_RTIPC_XDDP is enabled in the config. Doesn't
look like others have experienced this before. LinuxCNC doesn't use
XDDP, but it should be fixed for the general audience.
2) "clocktest -C 42 -T 30" fails; apparently expected in some
circumstances ('... || :'). Does anything need to be fixed here? The
test system switched to acpi_pm, and the TSCs on the dual-core are
unsynched. We don't know if the end-user's application will lock the
process to a single CPU, so CLOCK_HOST_REALTIME isn't the best choice,
even if it were somehow available.
3) "Warning: Linux is compiled to use FPU in kernel-space" in dmesg:
Ignoring: disabling (at least) software RAID breaks the
'one-size-fits-all' goal, and Gilles states this is harmless:
http://www.xenomai.org/pipermail/xenomai/2009-May/016743.html
John
current status:
xenomai-2.6 master 851281e5 (Sun Jan 13 13:51:22 2013 +0100)
ipipe-gch for-core-3.5.7 fde77b2e (Wed Jan 9 12:14:54 2013 +0100)
kernel .config
http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-kernel-config-3.5.7-test.txt
dmesg
http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-dmesg-3.5.7-test.log
regression test
http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-xeno-regression-test-3.5.7-test.log
next prev parent reply other threads:[~2013-01-15 7:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 17:26 [Xenomai] Kernel OOPS during regression tests John Morris
2013-01-12 17:31 ` Gilles Chanteperdrix
2013-01-13 4:36 ` John Morris
2013-01-13 12:16 ` Gilles Chanteperdrix
2013-01-13 19:14 ` [Xenomai] 3.5.7 "I-pipe: could not find timer" (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:41 ` Gilles Chanteperdrix
2013-01-14 4:47 ` [Xenomai] 3.5.7 posix/mprotect failure; "I-pipe: could not find timer" fixed! John Morris
2013-01-14 11:57 ` Gilles Chanteperdrix
2013-01-14 12:00 ` Jan Kiszka
2013-01-14 13:36 ` Jan Kiszka
2013-01-14 20:52 ` John Morris
2013-01-14 22:54 ` Gilles Chanteperdrix
2013-01-15 7:16 ` John Morris [this message]
2013-01-15 7:31 ` [Xenomai] 3.5.7 posix/mprotect fixed; (Was: posix/mprotect failure) Gilles Chanteperdrix
2013-01-18 3:56 ` John Morris
2013-01-18 4:31 ` Gilles Chanteperdrix
2013-01-14 19:50 ` [Xenomai] 3.5.7 posix/mprotect failure; "I-pipe: could not find timer" fixed! Gilles Chanteperdrix
2013-01-14 20:56 ` John Morris
2013-01-14 22:57 ` Gilles Chanteperdrix
2013-01-14 12:00 ` [Xenomai] 3.5.7 "I-pipe: could not find timer" (Was: Re: Kernel OOPS during regression tests) Jan Kiszka
2013-01-14 18:50 ` Gilles Chanteperdrix
2013-01-14 19:13 ` Jan Kiszka
2013-01-14 19:15 ` Gilles Chanteperdrix
2013-01-14 19:37 ` Jan Kiszka
2013-01-14 20:39 ` Gilles Chanteperdrix
2013-01-15 11:35 ` Jan Kiszka
2013-01-15 12:06 ` Gilles Chanteperdrix
2013-01-15 12:09 ` Philippe Gerum
2013-01-15 12:21 ` Jan Kiszka
2013-01-15 13:44 ` Philippe Gerum
2013-01-15 13:48 ` Jan Kiszka
2013-01-15 13:58 ` Philippe Gerum
2013-01-15 14:10 ` Jan Kiszka
2013-01-15 19:39 ` Gilles Chanteperdrix
2013-01-16 8:02 ` Jan Kiszka
2013-01-16 8:44 ` Jan Kiszka
2013-01-16 9:41 ` Philippe Gerum
2013-01-16 9:48 ` Jan Kiszka
2013-01-16 10:37 ` Philippe Gerum
2013-01-16 12:03 ` Gilles Chanteperdrix
2013-01-16 12:18 ` Jan Kiszka
2013-01-15 13:59 ` Jan Kiszka
2013-01-12 19:02 ` [Xenomai] Kernel OOPS during regression tests Gilles Chanteperdrix
2013-01-13 6:50 ` John Morris
2013-01-13 11:23 ` Jan Kiszka
2013-01-13 12:18 ` Gilles Chanteperdrix
2013-01-13 19:34 ` [Xenomai] 3.5.3 posix/mprotect fail "sigdebug_handler triggered" (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:42 ` Gilles Chanteperdrix
2013-01-12 19:03 ` [Xenomai] Kernel OOPS during regression tests Gilles Chanteperdrix
2013-01-13 4:40 ` John Morris
2013-01-13 13:53 ` Gilles Chanteperdrix
2013-01-13 19:36 ` [Xenomai] SMI workarounds in one-size-fits-all kernel packages (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:45 ` Gilles Chanteperdrix
2013-01-14 5:33 ` John Morris
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=50F5025E.1040500@zultron.com \
--to=john@zultron.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--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.