From: Andi Kleen <andi@firstfloor.org>
To: Erik Bosman <erik@minemu.org>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] x86: SROP mitigation: implement signal canaries
Date: Fri, 16 May 2014 18:03:01 +0200 [thread overview]
Message-ID: <20140516160301.GH1873@two.firstfloor.org> (raw)
In-Reply-To: <20140515223222.GA9727@pizzadoos.com>
> Hrmz.. FP state is aligned on a 64 byte boundary, the signal frame (separately)
> on a 16 byte-sizeof(long) boundary. But it looks like that for 32 and 64 bit
> rt_sigreturn this means no padding :-/
There may be some unused bytes in the existing structures, perhaps not
continuous.
-Andi
prev parent reply other threads:[~2014-05-16 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 21:10 [PATCH 2/4] x86: SROP mitigation: implement signal canaries Erik Bosman
2014-05-15 21:31 ` Andi Kleen
2014-05-15 22:32 ` Erik Bosman
2014-05-16 16:03 ` 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=20140516160301.GH1873@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=erik@minemu.org \
--cc=linux-kernel@vger.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