All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2
Date: Wed, 23 May 2007 11:32:53 -0400	[thread overview]
Message-ID: <46545EA5.3020201@redhat.com> (raw)

The recent changes in the 2.6.22-rc2 kernel to the write protection of read only 
data enable by CONFIG_DEBUG_RODATA prevents kprobes from working. At least on 
the on i386 and x86_64 machine the mark_rodata_ro() function marks memory 
starting from _text as read only. Thus, when kprobes attempts to write a break 
point into a location in the kernel it faults.

There is a description of the problem at:

http://sources.redhat.com/bugzilla/show_bug.cgi?id=4531

Shouldn't mark_rodata_ro be less agressive when CONFIG_KPROBES is enabled? Or 
should kprobes temporarily change the page to be writeable, set the break point, 
and then return the page to read only?

-Will

             reply	other threads:[~2007-05-23 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 15:32 William Cohen [this message]
2007-05-25 12:19 ` CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2 Andi Kleen

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=46545EA5.3020201@redhat.com \
    --to=wcohen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.