From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Handle SIGILL when kernel compiled without Xenomai.
Date: Mon, 22 Sep 2008 20:18:44 +0200 [thread overview]
Message-ID: <48D7E184.5000200@domain.hid> (raw)
In-Reply-To: <48D7BA7F.6030801@domain.hid>
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
>> Gilles Chanteperdrix wrote:
>>> Hi,
>>>
>>> on some (all ?) platforms, we get a SIGILL when trying to emit the first
>>> Xenomai syscall, instead of the -ENOSYS return value. This patches
>>> handles the SIGILL by printing an error message and exiting.
>>>
>> This is an issue for archs that encode the syscall number into the trap opcode
>> like ARM using the OABI, others will get -ENOSYS as expected, so this should
>> move to the arch-specific code.
>
> Actually, I get a SIGILL on ARM compiled with EABI as well. Moving this
> code to the arch dependent code looks hard, since we need to setup the
> jump buffer in the very function which issues the syscall (Ok, we could
> use a macro). But what would you think of a SIGILL handler which does
> not longjmp (like Jan suggested, simply print an error message and exit,
> even if xeno_bind_skin_opt was called) ?
>
So, here is another version.
Index: include/asm-generic/bits/bind.h
===================================================================
--- include/asm-generic/bits/bind.h (revision 4175)
+++ include/asm-generic/bits/bind.h (working copy)
@@ -99,15 +99,32 @@ static void unmap_sem_heap(unsigned long
}
#endif /* CONFIG_XENO_FASTSEM */
+void __attribute__((weak)) xeno_sigill_handler(int sig)
+{
+ fprintf(stderr, "Xenomai or CONFIG_XENO_OPT_PERVASIVE disabled.\n"
+ "(modprobe xeno_nucleus?)\n");
+ exit(1);
+}
+
static inline int
xeno_bind_skin(unsigned skin_magic, const char *skin, const char *module)
{
+ sighandler_t old_sigill_handler;
struct sigaction sa;
xnfeatinfo_t finfo;
int muxid;
+ old_sigill_handler = signal(SIGILL, xeno_sigill_handler);
+ if (old_sigill_handler == SIG_ERR) {
+ perror("signal(SIGILL)");
+ exit(1);
+ }
+
muxid = XENOMAI_SYSBIND(skin_magic,
XENOMAI_FEAT_DEP, XENOMAI_ABI_REV, &finfo);
+
+ signal(SIGILL, old_sigill_handler);
+
switch (muxid) {
case -EINVAL:
@@ -180,11 +197,21 @@ xeno_bind_skin(unsigned skin_magic, cons
static inline int
xeno_bind_skin_opt(unsigned skin_magic, const char *skin, const char *module)
{
+ sighandler_t old_sigill_handler;
xnfeatinfo_t finfo;
int muxid;
+ old_sigill_handler = signal(SIGILL, xeno_sigill_handler);
+ if (old_sigill_handler == SIG_ERR) {
+ perror("signal(SIGILL)");
+ exit(1);
+ }
+
muxid = XENOMAI_SYSBIND(skin_magic,
XENOMAI_FEAT_DEP, XENOMAI_ABI_REV, &finfo);
+
+ signal(SIGILL, old_sigill_handler);
+
switch (muxid) {
case -EINVAL:
--
Gilles.
next prev parent reply other threads:[~2008-09-22 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 20:01 [Xenomai-core] Handle SIGILL when kernel compiled without Xenomai Gilles Chanteperdrix
2008-09-22 8:25 ` Philippe Gerum
2008-09-22 15:32 ` Gilles Chanteperdrix
2008-09-22 18:18 ` Gilles Chanteperdrix [this message]
2008-09-28 14:31 ` Philippe Gerum
2008-09-28 14:39 ` Gilles Chanteperdrix
2008-09-28 14:49 ` Philippe Gerum
2008-09-22 9:14 ` Jan Kiszka
2008-09-22 9:21 ` Gilles Chanteperdrix
2008-09-22 10:43 ` Jan Kiszka
2008-09-22 12:03 ` 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=48D7E184.5000200@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rpm@xenomai.org \
--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.