Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760890AbXFJGYZ (ORCPT ); Sun, 10 Jun 2007 02:24:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757363AbXFJGYR (ORCPT ); Sun, 10 Jun 2007 02:24:17 -0400 Received: from py-out-1112.google.com ([64.233.166.182]:61635 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756850AbXFJGYQ (ORCPT ); Sun, 10 Jun 2007 02:24:16 -0400 Message-ID: <5640c7e00706092324kd0ea8e0pef4a4cd764fce5d3@mail.gmail.com> Date: Sun, 10 Jun 2007 18:24:15 +1200 From: "Ian McDonald" To: prasanna@in.ibm.com Subject: Re: [PATCH] Kprobes i386 fix for mark ro data Cc: "Andrew Morton" , "Andi Kleen" , "Jim Keniston" , "Chuck Ebbert" , "Linux Kernel Mailing List" , ananth@in.ibm.com, anil.s.keshavamurthy@intel.com, "David S. Miller" , "Patrick Andrieux" , "DCCP Mailing List" , jbeulich@novell.com, systemtap@sources.redhat.com In-Reply-To: <20070607042229.GA9350@in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5640c7e00706061347v42c9ecbahb5354f6687a70a78@mail.gmail.com> <46673B76.2090508@redhat.com> <5640c7e00706061612h62074699wdbd2725654a164@mail.gmail.com> <20070607042229.GA9350@in.ibm.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1431 Lines: 41 On 6/7/07, S. P. Prasanna wrote: > > >It faulted when it tried to write the breakpoint instruction into the > > >running kernel's executable code. Apparently the kernel code is now marked > > >read-only? > > > > > > > > Yes it would appear to be the case as user has CONFIG_DEBUG_RODATA > > set. Patrick - can you turn this off and retest? It's under Kernel > > Hacking, Write protect kernel read only data structures. > > > > Ian, > > Please find the fix as suggested by Andi Kleen > for the above stated problem. > > Thanks > Prasanna > > I went to test the fix and first of all went to replicate the problem. My build has CONFIG_DEBUG_RODATA set but the problem does not occur without the patch. Should I be concerned about this and raise a bug for that as I would think that means there is a problem that the read only protection isn't working (this is off Linus' tree synced tonight). Patrick - can you test whether this patch fixes your problem? You said disabling CONFIG_DEBUG_RODATA fixed your problem but can you try re-enabling and testing this patch? Ian -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz WAND Network Research Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/