Re: CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2

2007-05-25 Thread Andi Kleen
William Cohen <[EMAIL PROTECTED]> writes: > > 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? The later. -Andi - To unsubscribe from this

Re: CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2

2007-05-25 Thread Andi Kleen
William Cohen [EMAIL PROTECTED] writes: 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? The later. -Andi - To unsubscribe from this list:

CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2

2007-05-23 Thread William Cohen
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

CONFIG_DEBUG_RODATA prevents kprobes from working on 2.6.22-rc2

2007-05-23 Thread William Cohen
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