From: Chuck Ebbert <76306.1226@compuserve.com>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>,
discuss@x86-64.org
Subject: Re: ptrace denies access to EFLAGS_RF
Date: Fri, 6 Jan 2006 11:10:16 -0500 [thread overview]
Message-ID: <200601061112_MC3-1-B567-47BB@compuserve.com> (raw)
In-Reply-To: <20060106140217.GD7676@frankl.hpl.hp.com>
On Fri, 6 Jan 2006 at 06:02:17 -0800, Stephane Eranian wrote:
> To my surprise, applying the same fix to the x86_64 does not
> solve the problem on my Opteron box. I verified that the
> offset (144) matches with what the kernel is expecting.
> Somehow the RF is lost or not set in the proper location.
> I cannot make forward progress once I reach the breakpoint.
I sent this to Andi this morning. Does it work for you?
Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
arch/x86_64/ia32/ptrace32.c | 9 ++++++---
arch/x86_64/kernel/ptrace.c | 9 ++++++---
2 files changed, 12 insertions(+), 6 deletions(-)
--- 2.6.15-64a.orig/arch/x86_64/ia32/ptrace32.c
+++ 2.6.15-64a/arch/x86_64/ia32/ptrace32.c
@@ -28,9 +28,12 @@
#include <asm/i387.h>
#include <asm/fpu32.h>
-/* determines which flags the user has access to. */
-/* 1 = access 0 = no access */
-#define FLAG_MASK 0x44dd5UL
+/*
+ * Determines which flags the user has access to [1 = access, 0 = no access].
+ * Prohibits changing ID(21), VIP(20), VIF(19), VM(17), IOPL(12-13), IF(9).
+ * Also masks reserved bits (31-22, 15, 5, 3, 1).
+ */
+#define FLAG_MASK 0x54dd5UL
#define R32(l,q) \
case offsetof(struct user32, regs.l): stack[offsetof(struct pt_regs, q)/8] = val; break
--- 2.6.15-64a.orig/arch/x86_64/kernel/ptrace.c
+++ 2.6.15-64a/arch/x86_64/kernel/ptrace.c
@@ -36,9 +36,12 @@
* in exit.c or in signal.c.
*/
-/* determines which flags the user has access to. */
-/* 1 = access 0 = no access */
-#define FLAG_MASK 0x44dd5UL
+/*
+ * Determines which flags the user has access to [1 = access, 0 = no access].
+ * Prohibits changing ID(21), VIP(20), VIF(19), VM(17), IOPL(12-13), IF(9).
+ * Also masks reserved bits (63-22, 15, 5, 3, 1).
+ */
+#define FLAG_MASK 0x54dd5UL
/* set's the trap flag. */
#define TRAP_FLAG 0x100UL
--
Chuck
Currently reading: _Thud!_ by Terry Pratchett
next reply other threads:[~2006-01-06 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 16:10 Chuck Ebbert [this message]
2006-01-12 22:11 ` Stephane Eranian
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 4:11 Chuck Ebbert
2006-01-06 9:39 ` Stephane Eranian
2006-01-06 14:02 ` Stephane Eranian
2006-01-05 10:51 Stephane Eranian
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=200601061112_MC3-1-B567-47BB@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=eranian@hpl.hp.com \
--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
all inboxes | Powered by JetHome®