linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org,
	linux-kernel@vger.rutgers.edu
Subject: Re: nasty powerpc mmap problems (was: Re: Vger broken w.r.t. gdb)
Date: Sun, 1 Aug 1999 22:45:36 -0400	[thread overview]
Message-ID: <19990801224536.A376@them.org> (raw)
In-Reply-To: <19990730030738.A1450@them.org>; from Daniel Jacobowitz on Fri, Jul 30, 1999 at 03:07:39AM -0400

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

I think I've found the problem.  access_process_vm() would trigger a
page fault for write if the page was unmapped, but not if it was
already mapped for read.  The attached patch fixed all my problems.


On Fri, Jul 30, 1999 at 03:07:39AM -0400, Daniel Jacobowitz wrote:
> [CC me in replies, I'm not on linux-kernel]
> 
> Background from the thread on linuxppc-dev: with the current vger tree,
> gdb's breakpoints are apparently being set in the wrong copy of a
> shared library, and not properly removed.  After running gdb over any
> program, even with no extra breakpoints set, every dynamically linked
> program run inside or outside of gdb dies with SIGTRAP.  The SIGTRAP
> appears to be in _dl_debug_state or thereabouts in ld.so.

...

> I've found a much simpler test case for this problem.  It seems to me
> to be more than ptrace being broken.  I wrote two test programs; mmap1
> merely opens a file, mmaps it, closes it, prints some debugging info,
> sleeps, and prints a little more.  Notice the permissions:
>   int fd = open("testfile", O_RDONLY);
>   ptr = mmap(0, 0x4000, PROT_READ|PROT_EXEC, MAP_SHARED, fd, 0);
>   close(fd);


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

[-- Attachment #2: fix-ptrace.diff --]
[-- Type: text/plain, Size: 539 bytes --]

Index: ptrace.c
===================================================================
RCS file: /cvs/linux/linux/kernel/ptrace.c,v
retrieving revision 1.2
diff -c -p -r1.2 ptrace.c
*** ptrace.c	1999/07/23 02:04:32	1.2
--- ptrace.c	1999/08/02 02:23:45
*************** repeat:
*** 38,43 ****
--- 38,45 ----
  	pgtable = pte_offset(pgmiddle, addr);
  	if (!pte_present(*pgtable))
  		goto fault_in_page;
+ 	if (write && !pte_write(*pgtable))
+ 		goto fault_in_page;
  	page = pte_page(*pgtable);
  	if (MAP_NR(page) >= max_mapnr)
  		return 0;

      reply	other threads:[~1999-08-02  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-29  2:26 Vger broken w.r.t. gdb Daniel Jacobowitz
1999-07-29  4:00 ` Paul Mackerras
1999-07-29  5:38   ` Daniel Jacobowitz
1999-07-29  5:48     ` Paul Mackerras
1999-07-30  5:18       ` Daniel Jacobowitz
1999-07-30  5:24         ` Paul Mackerras
1999-07-30  6:03           ` Daniel Jacobowitz
1999-07-30  7:07           ` nasty powerpc mmap problems (was: Re: Vger broken w.r.t. gdb) Daniel Jacobowitz
1999-08-02  2:45             ` Daniel Jacobowitz [this message]

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=19990801224536.A376@them.org \
    --to=drow@false.org \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).