All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp-cmBhpYW9OiY@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>,
	Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Shuah Khan <shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v6 0/4] make sigaltstack() compatible with swapcontext()
Date: Fri, 25 Mar 2016 23:16:57 +0300	[thread overview]
Message-ID: <56F59CB9.9030203@list.ru> (raw)
In-Reply-To: <1457369527-11452-1-git-send-email-stsp-cmBhpYW9OiY@public.gmane.org>

So what is the status of the below?
I haven't seen any NAKs or objections, yet it seems not
applied 3 weeks later. What should I do now?

07.03.2016 19:52, Stas Sergeev пишет:
> The following patches make it possible to use swapcontext()
> in a sighandler that works on sigaltstack.
> The approach is inspired by Andy Lutomirski's suggestion that
> sigaltstack should disarm itself after saving into uc_stack:
> https://lkml.org/lkml/2016/2/1/594
>
> I add the SS_AUTODISARM flag that does exactly that.
> On sighandler exit, the sigaltstack is restored from uc_stack.
> Another possible name could be SS_ONESHOT, but, since it gets
> always re-enabled, I choose SS_AUTODISARM.
>
> Change since v5:
> - Fix description of patch 4/4
>
> Change since v4:
> - Implement this Andy Lutomirski's suggestion:
> https://lkml.org/lkml/2016/3/6/158
> that allows the run-time probing of the existence of the
> flags added in the future.
>
> [PATCH 1/4] [Cleanup] x86: signal: unify the sigaltstack check with
> 	A clean-up patch that unifies x86's sigaltstack handling with
> 	other arches.
> [PATCH 2/4] sigaltstack: preparations for adding new SS_xxx flags
> 	Andy's suggested changes
> [PATCH 3/4] sigaltstack: implement SS_AUTODISARM flag
> 	This patch implements SS_AUTODISARM flag
> [PATCH 4/4] selftests: Add test for
> 	This patch adds the selftest code for new functionality
>
> CC: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> CC: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> CC: Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
> CC: Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> CC: Shuah Khan <shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
> CC: Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>
> Diffstat:
>   arch/x86/kernel/signal.c                     |   23 +--
>   include/linux/sched.h                        |    8 +
>   include/linux/signal.h                       |    4
>   include/uapi/linux/signal.h                  |    7 +
>   kernel/fork.c                                |    2
>   kernel/signal.c                              |   26 ++--
>   tools/testing/selftests/Makefile             |    1
>   tools/testing/selftests/sigaltstack/Makefile |    8 +
>   tools/testing/selftests/sigaltstack/sas.c    |  156 +++++++++++++++++++++++++++
>   9 files changed, 208 insertions(+), 27 deletions(-)
>
>

WARNING: multiple messages have this Message-ID (diff)
From: Stas Sergeev <stsp@list.ru>
To: unlisted-recipients:; (no To-header on input)
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>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v6 0/4] make sigaltstack() compatible with swapcontext()
Date: Fri, 25 Mar 2016 23:16:57 +0300	[thread overview]
Message-ID: <56F59CB9.9030203@list.ru> (raw)
In-Reply-To: <1457369527-11452-1-git-send-email-stsp@list.ru>

So what is the status of the below?
I haven't seen any NAKs or objections, yet it seems not
applied 3 weeks later. What should I do now?

07.03.2016 19:52, Stas Sergeev пишет:
> The following patches make it possible to use swapcontext()
> in a sighandler that works on sigaltstack.
> The approach is inspired by Andy Lutomirski's suggestion that
> sigaltstack should disarm itself after saving into uc_stack:
> https://lkml.org/lkml/2016/2/1/594
>
> I add the SS_AUTODISARM flag that does exactly that.
> On sighandler exit, the sigaltstack is restored from uc_stack.
> Another possible name could be SS_ONESHOT, but, since it gets
> always re-enabled, I choose SS_AUTODISARM.
>
> Change since v5:
> - Fix description of patch 4/4
>
> Change since v4:
> - Implement this Andy Lutomirski's suggestion:
> https://lkml.org/lkml/2016/3/6/158
> that allows the run-time probing of the existence of the
> flags added in the future.
>
> [PATCH 1/4] [Cleanup] x86: signal: unify the sigaltstack check with
> 	A clean-up patch that unifies x86's sigaltstack handling with
> 	other arches.
> [PATCH 2/4] sigaltstack: preparations for adding new SS_xxx flags
> 	Andy's suggested changes
> [PATCH 3/4] sigaltstack: implement SS_AUTODISARM flag
> 	This patch implements SS_AUTODISARM flag
> [PATCH 4/4] selftests: Add test for
> 	This patch adds the selftest code for new functionality
>
> CC: linux-kernel@vger.kernel.org
> CC: linux-api@vger.kernel.org
> CC: Andy Lutomirski <luto@amacapital.net>
> CC: Oleg Nesterov <oleg@redhat.com>
> CC: Shuah Khan <shuahkh@osg.samsung.com>
> CC: Ingo Molnar <mingo@redhat.com>
>
> Diffstat:
>   arch/x86/kernel/signal.c                     |   23 +--
>   include/linux/sched.h                        |    8 +
>   include/linux/signal.h                       |    4
>   include/uapi/linux/signal.h                  |    7 +
>   kernel/fork.c                                |    2
>   kernel/signal.c                              |   26 ++--
>   tools/testing/selftests/Makefile             |    1
>   tools/testing/selftests/sigaltstack/Makefile |    8 +
>   tools/testing/selftests/sigaltstack/sas.c    |  156 +++++++++++++++++++++++++++
>   9 files changed, 208 insertions(+), 27 deletions(-)
>
>

  parent reply	other threads:[~2016-03-25 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 16:52 [PATCH v6 0/4] make sigaltstack() compatible with swapcontext() Stas Sergeev
2016-03-07 16:52 ` Stas Sergeev
2016-03-07 16:52 ` [PATCH 1/4] [Cleanup] x86: signal: unify the sigaltstack check with other arches Stas Sergeev
2016-03-07 16:52 ` [PATCH 2/4] sigaltstack: preparations for adding new SS_xxx flags Stas Sergeev
2016-03-07 16:52 ` [PATCH 4/4] selftests: Add test for sigaltstack(SS_ONSTACK|SS_AUTODISARM) Stas Sergeev
     [not found] ` <1457369527-11452-1-git-send-email-stsp-cmBhpYW9OiY@public.gmane.org>
2016-03-07 16:52   ` [PATCH 3/4] sigaltstack: implement SS_AUTODISARM flag Stas Sergeev
2016-03-07 16:52     ` Stas Sergeev
2016-03-25 20:16   ` Stas Sergeev [this message]
2016-03-25 20:16     ` [PATCH v6 0/4] make sigaltstack() compatible with swapcontext() Stas Sergeev

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=56F59CB9.9030203@list.ru \
    --to=stsp-cmbhpyw9oiy@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
    --cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.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.