From: <tartanllama@gmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: ptrace: Why does PTRACE_PEEKUSER not allow reading of FPU registers on x86?
Date: Wed, 21 Feb 2024 12:39:23 -0000 [thread overview]
Message-ID: <01a401da64c3$0027ce60$00776b20$@gmail.com> (raw)
Hey folks,
Looking at arch/x86/kernel/ptrace.c, I can see that reading with
PTRACE_PEEKUSER is only supported within the user::regs and user::u_debugreg
fields. What's the reason that reading from user::i387 is disallowed?
Thanks,
Sy Brand
reply other threads:[~2024-02-21 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='01a401da64c3$0027ce60$00776b20$@gmail.com' \
--to=tartanllama@gmail.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