From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@alien8.de>, Stas Sergeev <stsp@list.ru>,
Al Viro <viro@zeniv.linux.org.uk>,
Aleksa Sarai <cyphar@cyphar.com>,
"Amanieu d'Antras" <amanieu@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jason Low <jason.low2@hp.com>,
Josh Triplett <josh@joshtriplett.org>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Moore <pmoore@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
Peter Zijlstra <peterz@infradead.org>,
Richard Weinberger <richard@nod.at>,
Sasha Levin <sasha.levin@oracle.com>,
Shuah Khan <shuahkh@osg.samsung.com>, Tejun Heo <tj@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vladimir Davydov <vdavydov@parallels.com>,
linux-api@vger.kernel.org
Subject: Re: [PATCH 1/4] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack
Date: Wed, 4 May 2016 08:32:33 +0200 [thread overview]
Message-ID: <20160504063233.GB9499@gmail.com> (raw)
In-Reply-To: <c46bee4654ca9e68c498462fd11746e2bd0d98c8.1462296606.git.luto@kernel.org>
* Andy Lutomirski <luto@kernel.org> wrote:
> If a signal stack is set up with SS_AUTODISARM, then the kernel
> inherently avoids incorrectly resetting the signal stack if signals
> recurse: the signal stack will be reset on the first signal
> delivery. This means that we don't need check the stack pointer
> when delivering signals if SS_AUTODISARM is set.
>
> This will make segmented x86 programs more robust: currently there's
> a hole that could be triggered if ESP/RSP appears to point to the
> signal stack but actually doesn't due to a nonzero SS base.
>
> Signed-off-by: Stas Sergeev <stsp@list.ru>
Presuably that SOB from Stas is stray, as there's no matching From: line?
I've removed it.
Thanks,
Ingo
next prev parent reply other threads:[~2016-05-04 6:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:31 [PATCH 0/4] SS_AUTODISARM fixes and an ABI change Andy Lutomirski
2016-05-03 17:31 ` [PATCH 1/4] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack Andy Lutomirski
2016-05-04 6:32 ` Ingo Molnar [this message]
2016-05-04 23:02 ` Andy Lutomirski
2016-05-04 7:12 ` [tip:core/signals] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack() tip-bot for Andy Lutomirski
2016-05-07 14:37 ` [PATCH 1/4] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack Stas Sergeev
2016-05-09 1:32 ` Andy Lutomirski
2016-05-09 2:04 ` Stas Sergeev
2016-05-14 4:18 ` Andy Lutomirski
2016-05-14 11:18 ` Stas Sergeev
2016-05-14 16:35 ` Andy Lutomirski
2016-05-03 17:31 ` [PATCH 2/4] selftests/sigaltstack: Fix the sas test on old kernels Andy Lutomirski
2016-05-04 7:13 ` [tip:core/signals] selftests/sigaltstack: Fix the sigaltstack " tip-bot for Andy Lutomirski
2016-05-07 15:02 ` [PATCH 2/4] selftests/sigaltstack: Fix the sas " Stas Sergeev
2016-05-09 1:32 ` Andy Lutomirski
2016-05-03 17:31 ` [PATCH 3/4] signals/sigaltstack: Report current flag bits in sigaltstack() Andy Lutomirski
2016-05-04 6:33 ` Ingo Molnar
2016-05-04 7:13 ` [tip:core/signals] " tip-bot for Andy Lutomirski
2016-05-03 17:31 ` [PATCH 4/4] signals/sigaltstack: Change SS_AUTODISARM to (1U << 31) Andy Lutomirski
2016-05-04 7:13 ` [tip:core/signals] " tip-bot for Andy Lutomirski
2016-05-07 15:16 ` [PATCH 4/4] " Stas Sergeev
2016-05-04 6:25 ` [PATCH 0/4] SS_AUTODISARM fixes and an ABI change Ingo Molnar
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=20160504063233.GB9499@gmail.com \
--to=mingo@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amanieu@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=cyphar@cyphar.com \
--cc=dvlasenk@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jason.low2@hp.com \
--cc=josh@joshtriplett.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pmoore@redhat.com \
--cc=richard@nod.at \
--cc=sasha.levin@oracle.com \
--cc=shuahkh@osg.samsung.com \
--cc=stsp@list.ru \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdavydov@parallels.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
--cc=xemul@parallels.com \
--cc=xypron.glpk@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).