From: Jan Kiszka <jan.kiszka@domain.hid>
To: Hannes Mayer <h.mayer@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] racy xnshadow_harden under CONFIG_PREEMPT
Date: Sat, 21 Jan 2006 18:01:59 +0100 [thread overview]
Message-ID: <43D26907.8020900@domain.hid> (raw)
In-Reply-To: <43D265A8.1020407@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Hannes Mayer wrote:
> Jan Kiszka wrote:
> [...]
>> PS: Out of curiosity I also checked RTAI's migration mechanism in this
>> regard. It's similar except for the fact that it does the gatekeeper's
>> work in the Linux scheduler's tail (i.e. after the next context switch).
>> And RTAI seems it suffers from the very same race. So this is either a
>> fundamental issue - or I'm fundamentally wrong.
>
>
> Well, most of the stuff you guys talk about in this thread is still
> beyond my level, but out of curiosity I ported the SEM example to
> RTAI (see attached sem.c)
> I couldn't come up with something similar to rt_sem_inquire and
> rt_task_inquire in RTAI (in "void output(char c)")...
> Anyway, unless I haven't missed something else important while
> porting, the example runs flawlessly on RTAI 3.3test3 (kernel 2.6.15).
>
My claim on the RTAI race is based on quick code analysis and a bit
outdated information about its core design. I haven't tried any code to
crash it, and I guess it will take a slightly different test design to
trigger the issue there. As soon as someone could follow my reasoning
and confirm it (don't mind that you did not understand it, I hadn't
either two days ago, this is quite heavy stuff), I will inform Paolo
about this potential problem.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-01-21 17:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 10:47 [Xenomai-core] [BUG] racy xnshadow_harden under CONFIG_PREEMPT Jan Kiszka
2006-01-21 10:51 ` [Xenomai-core] " Jeroen Van den Keybus
2006-01-21 16:47 ` [Xenomai-core] " Hannes Mayer
2006-01-21 17:01 ` Jan Kiszka [this message]
2006-01-22 8:10 ` Dmitry Adamushko
2006-01-22 16:19 ` Jeroen Van den Keybus
2006-01-23 18:22 ` Gilles Chanteperdrix
2006-01-23 19:16 ` Jan Kiszka
2006-01-30 14:51 ` Philippe Gerum
2006-01-30 15:33 ` Philippe Gerum
2006-01-30 16:01 ` Jan Kiszka
2006-01-30 23:10 ` Philippe Gerum
2006-01-31 19:01 ` Jan Kiszka
2006-01-30 15:35 ` Philippe Gerum
2006-01-31 21:09 ` Jeroen Van den Keybus
2006-01-31 21:45 ` Philippe Gerum
2006-02-01 9:57 ` Jeroen Van den Keybus
2006-02-01 10:03 ` Jan Kiszka
2006-02-01 12:23 ` Jeroen Van den Keybus
2006-02-01 12:34 ` Jan Kiszka
2006-01-24 13:14 ` Dmitry Adamushko
2006-01-24 13:26 ` Jan Kiszka
2006-01-30 11:37 ` Dmitry Adamushko
2006-01-30 11:48 ` Jan Kiszka
2006-01-30 13:02 ` Dmitry Adamushko
2006-01-29 23:48 ` Philippe Gerum
2006-01-30 10:14 ` Philippe Gerum
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=43D26907.8020900@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=h.mayer@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.