From: Andi Kleen <ak@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Scotty Bauer" <sbauer@eng.utah.edu>,
"Mika Penttilä" <mika.penttila@nextfour.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>, "X86 ML" <x86@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Abhiram Balasubramanian" <abhiram@cs.utah.edu>
Subject: Re: [PATCHv2 2/2] x86: SROP mitigation: implement signal cookies
Date: Tue, 9 Feb 2016 12:45:54 -0800 [thread overview]
Message-ID: <20160209204554.GD4875@tassilo.jf.intel.com> (raw)
In-Reply-To: <CALCETrW_ingsNEwBKKYbkugt5OsG8K6HUs22ZF+Lxc24iy8tTg@mail.gmail.com>
> Is this compatible with existing userspace? CRIU and DOSEMU seem like
> things that are likely to blow up to me.
It should at least make it a sysctl.
>
> We may need to make this type of mitigation be opt-in. I'm already
> vaguely planning an opt-in mitigation framework for vsyscall runtime
> disablement, and this could use the same opt-in mechanism.
Generally asking people to rely on frame works that don't exist
is not good review feedback.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2016-02-09 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 23:39 [PATCHv2 0/2] SROP Mitigation: Signal cookies Scott Bauer
2016-02-06 23:39 ` [PATCHv2 1/2] SROP Mitigation: Architecture independent code for signal cookies Scott Bauer
2016-02-06 23:39 ` [PATCHv2 2/2] x86: SROP mitigation: implement " Scott Bauer
2016-02-07 6:35 ` Mika Penttilä
2016-02-07 8:10 ` Scotty Bauer
2016-02-08 21:50 ` Andy Lutomirski
2016-02-08 23:17 ` Scotty Bauer
2016-02-09 5:51 ` Andy Lutomirski
2016-02-09 20:45 ` Andi Kleen [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=20160209204554.GD4875@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=abhiram@cs.utah.edu \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mika.penttila@nextfour.com \
--cc=mingo@redhat.com \
--cc=sbauer@eng.utah.edu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome