From: Juan Quintela <quintela@mandrakesoft.com>
To: Jun Sun <jsun@mvista.com>
Cc: Vivien Chappelier <vivienc@nerim.net>,
Ralf Baechle <ralf@oss.sgi.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH 2.5] clear USEDFPU in copy_thread
Date: Fri, 07 Feb 2003 02:20:58 +0100 [thread overview]
Message-ID: <86hebgj37p.fsf@trasno.mitica> (raw)
In-Reply-To: <20030206164342.G13258@mvista.com> (Jun Sun's message of "Thu, 6 Feb 2003 16:43:42 -0800")
>>>>> "jun" == Jun Sun <jsun@mvista.com> writes:
Hi
jun> Even if you don't have it cleared in start_thread(), things
jun> should be generally OK. You will have some dirty FPU content
jun> instead of a all-zero one when you start a new program. But then
jun> since all sane program should assign register values before they
jun> first time use them, so this bug should be well hidden.
I don't remind the exact details, but the problem appears to be the
security implications, you can see last values of previous process.
Yes, I still have to find a way where that is useful, but ...
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-02-07 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 22:54 [PATCH 2.5] clear USEDFPU in copy_thread Vivien Chappelier
2003-02-07 0:43 ` Jun Sun
2003-02-07 1:20 ` Juan Quintela [this message]
2003-02-07 18:46 ` Jun Sun
2003-02-07 22:13 ` Vivien Chappelier
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=86hebgj37p.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@oss.sgi.com \
--cc=vivienc@nerim.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.