From: Szabolcs Nagy <nsz@port70.net>
To: Stas Sergeev <stsp@list.ru>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v4 0/2] make sigaltstack() compatible with swapcontext()
Date: Sun, 6 Mar 2016 21:27:38 +0100 [thread overview]
Message-ID: <20160306202738.GU29662@port70.net> (raw)
In-Reply-To: <20160306200207.GT29662@port70.net>
* Szabolcs Nagy <nsz@port70.net> [2016-03-06 21:02:08 +0100]:
> * Stas Sergeev <stsp@list.ru> [2016-03-01 00:29:03 +0300]:
> > The following patches make it possible to use swapcontext()
> > in a sighandler that works on sigaltstack.
>
> i don't think that's possible, the (obsolete) userspace
> *context functions cannot operate on kernel provided
> ucontext_t structs, so they are not usable in signal
> handlers.
>
> at least not on most target archs.
>
> so i don't understand how the tests can work portably.
>
i see the test does not use the kernel ucontext_t
and only synchronous context switch is done
sorry for the noise.
prev parent reply other threads:[~2016-03-06 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 21:29 Stas Sergeev
2016-02-29 21:29 ` [PATCH 1/2] sigaltstack: implement SS_AUTODISARM flag Stas Sergeev
2016-03-04 22:22 ` Andy Lutomirski
2016-03-05 7:39 ` Stas Sergeev
2016-03-05 7:40 ` Stas Sergeev
2016-03-06 20:07 ` Andy Lutomirski
2016-03-06 20:10 ` Andy Lutomirski
2016-03-06 20:17 ` Stas Sergeev
2016-03-06 20:55 ` Andy Lutomirski
2016-02-29 21:29 ` [PATCH 2/2] selftests: Add test for sigaltstack(SS_AUTODISARM) Stas Sergeev
2016-03-06 20:02 ` [PATCH v4 0/2] make sigaltstack() compatible with swapcontext() Szabolcs Nagy
2016-03-06 20:27 ` Stas Sergeev
2016-03-06 20:27 ` Szabolcs Nagy [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=20160306202738.GU29662@port70.net \
--to=nsz@port70.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=shuahkh@osg.samsung.com \
--cc=stsp@list.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®