From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall
Date: Mon, 22 Jun 2015 10:19:28 +0200 [thread overview]
Message-ID: <5587C510.10306@siemens.com> (raw)
In-Reply-To: <f7e5785057e2a9f6fe8374e56cd44d47.squirrel@sourcetrek.com>
On 2015-06-20 16:41, Gilles Chanteperdrix wrote:
>
> git repository hosting wrote:
>> Module: xenomai-jki
>> Branch: for-forge
>> Commit: c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa
>> URL:
>> http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa
>>
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Fri Jun 19 15:59:15 2015 +0200
>>
>> cobalt/kernel: Fix mode of mayday syscall
>>
>> The oneway mode meant norestart, thus return -EINTR instead of retrying
>> the syscall after signal processing. But this caused damaged to the
>> register state of the mayday-interrupted thread, most visible on x86-64
>> where RAX is holding the RIP.
>
> And this can not be fixed, because ?
There are probably more ways to fix it. One I played with as well was
manipulating the mayday page's stack from the kernel, thus its return
address (in the hope it would fix the backtrace too, but it didn't).
But this patch is obsolete if the mayday simplification patch pushed
yesterday can be merged for all archs.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2015-06-22 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Z6JYL-0001WU-7T@sd-51317.xenomai.org>
2015-06-20 14:41 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall Gilles Chanteperdrix
2015-06-22 8:19 ` Jan Kiszka [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=5587C510.10306@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@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.