From: Richard Weinberger <richard@nod.at>
To: Eli Cooper <elicooper@gmx.com>,
user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [PATCH] um: fix FPU register double-restore after sigreturn
Date: Thu, 17 Mar 2016 23:21:44 +0100 [thread overview]
Message-ID: <56EB2DF8.8030102@nod.at> (raw)
In-Reply-To: <1458091505-967-1-git-send-email-elicooper@gmx.com>
Eli,
Am 16.03.2016 um 02:25 schrieb Eli Cooper:
> This patch prevents userspace() from incorrectly restoring FPU registers
> after a sigreturn or rt_sigreturn system call, which has already restored
> FPU registers to the state prior to the signal handler was invoked.
>
> Fixes FPU state corruption after invoking the signal handler.
First of all, thanks a lot for hunting down these nasty issues!
Where exactly are the FPU regs restored in the sigregturn case?
Not sure if I fully understand the error scenario.
Thanks,
//richard
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2016-03-17 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 1:25 [uml-devel] [PATCH] um: fix FPU register double-restore after sigreturn Eli Cooper
2016-03-17 22:21 ` Richard Weinberger [this message]
2016-03-18 1:41 ` Eli Cooper
2016-03-18 8:20 ` Richard Weinberger
2016-03-18 16:13 ` Eli Cooper
2016-03-18 16:42 ` Jeff Dike
2016-03-18 20:12 ` Richard Weinberger
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=56EB2DF8.8030102@nod.at \
--to=richard@nod.at \
--cc=elicooper@gmx.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).