From: David Howells <dhowells@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: bryan.wu@analog.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] utrace: nommu fixup support utrace
Date: Wed, 07 Mar 2007 11:10:37 +0000 [thread overview]
Message-ID: <7689.1173265837@redhat.com> (raw)
In-Reply-To: <20070307034216.472921801C4@magilla.sf.frob.com>
Roland McGrath <roland@redhat.com> wrote:
> That old ptrace check seems pretty questionable to me. I think what you
> want is for the nommu world's get_user_pages/access_process_vm when called
> with force=1,write=1 on a read-only MAP_PRIVATE page to do something more
> morally similar to the mmu world's COW than it does now.
Such as what? You *can't* do COW without relocating all the pointers userspace
may have into that VMA. However, unless you force non-sharing of R/O
MAP_PRIVATE VMAs, you will have text segments of executables and libraries
shared with other processes. Imagine: you set a breakpoint in uclibc read()
and your whole system dies instantly.
What I did is to say that if a process has PT_TRACED set then the MAP_PRIVATE
VMAs start with their own copies. The debugger can set this in a new process
by cloning it with appropriate CLONE_xxx flags.
It's not perfect, I know, but it's the best I could come up with as a solution
to debugging things in a NOMMU environment that supports shared libraries and
executables.
David
next prev parent reply other threads:[~2007-03-07 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 7:25 [PATCH -mm] utrace: nommu fixup support utrace Wu, Bryan
2007-03-06 9:37 ` David Howells
2007-03-06 9:49 ` Wu, Bryan
2007-03-07 3:42 ` Roland McGrath
2007-03-07 11:10 ` David Howells [this message]
2007-03-09 7:37 ` Roland McGrath
2007-03-09 11:41 ` David Howells
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=7689.1173265837@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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