From: Roland McGrath <roland@redhat.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Cagney <cagney@redhat.com>
Subject: Re: More trouble with i386 EFLAGS and ptrace
Date: Mon, 7 Mar 2005 13:29:12 -0800 [thread overview]
Message-ID: <200503072129.j27LTCnl030702@magilla.sf.frob.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of Sunday, 6 March 2005 23:49:20 -0500 <20050307044920.GA25093@nevyn.them.org>
> Is this semantically different from the patch I posted, i.e. is there
> any case which one of them covers and not the other?
Yes, the second case that I described when I said there were two cases!
(Sheesh.) To repeat, when the process was doing PTRACE_SINGLESTEP and then
stops on some other signal rather than because of the single-step trap
(e.g. single-stepping an instruction that faults), ptrace will show TF set
in its registers. With my patch, it will show TF clear.
> That is an inability to set breakpoints in the vsyscall page. Andrew
> told me (last May, wow) that he thought this worked in Fedora, but I
> haven't seen any signs of the code. It would certainly be a Good Thing
> if it is possible!
Fedora kernels use a normal mapping (with randomized location) for the
page, rather than the fixed high address in the vanilla kernel. The
FIXADDR_USER_START area is globally mapped in a special way not using
normal vma data structures, and is permanently read-only in all tasks.
COW via ptrace works normally for Fedora's flavor, but no writing is ever
possible to the fixmap page.
Thanks,
Roland
next prev parent reply other threads:[~2005-03-07 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 19:38 Daniel Jacobowitz
2005-03-06 20:03 ` Linus Torvalds
2005-03-06 21:14 ` Daniel Jacobowitz
2005-03-07 0:46 ` Linus Torvalds
2005-03-06 21:22 ` Roland McGrath
2005-03-06 22:13 ` Daniel Jacobowitz
[not found] ` <200503070316.j273Gb4G027048@magilla.sf.frob.com>
2005-03-07 4:49 ` Daniel Jacobowitz
2005-03-07 21:29 ` Roland McGrath [this message]
2005-03-09 0:12 ` Daniel Jacobowitz
2005-03-13 8:27 ` Roland McGrath
2005-03-13 20:06 ` Daniel Jacobowitz
2005-03-07 19:13 ` Andi Kleen
2005-03-06 20:26 ` Daniel Jacobowitz
2005-03-14 4:06 Jesse Allen
2005-03-14 4:12 Jesse Allen
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=200503072129.j27LTCnl030702@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=cagney@redhat.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®