linux-kernel - Re: [PATCH v6 0/4] make sigaltstack() compatible with swapcontext()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56F59CB9.9030203@list.ru>
Date:	Fri, 25 Mar 2016 23:16:57 +0300
From:	Stas Sergeev <stsp@...t.ru>
To:	unlisted-recipients:; (no To-header on input)
Cc:	linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
	Andy Lutomirski <luto@...capital.net>,
	Oleg Nesterov <oleg@...hat.com>,
	Shuah Khan <shuahkh@....samsung.com>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH v6 0/4] make sigaltstack() compatible with swapcontext()

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@...r.kernel.org
> CC: linux-api@...r.kernel.org
> CC: Andy Lutomirski <luto@...capital.net>
> CC: Oleg Nesterov <oleg@...hat.com>
> CC: Shuah Khan <shuahkh@....samsung.com>
> CC: Ingo Molnar <mingo@...hat.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(-)
>
>