From: Chuck Ebbert <cebbert@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: [BUG] Fwd: segfault : modprobe dccp_probe/tcp_probe
Date: Wed, 06 Jun 2007 22:55:50 +0000 [thread overview]
Message-ID: <46673B76.2090508@redhat.com> (raw)
In-Reply-To: <5640c7e00706061347v42c9ecbahb5354f6687a70a78@mail.gmail.com>
On 06/06/2007 04:47 PM, Ian McDonald wrote:
> Hi there,
>
> We've seen a report of a problem with dccp_probe as shown below. The
> user has also verified that it occurs in tcp_probe as well. This is on
> Dave Miller's tree but that currently tracks Linus' tree quite
> closely. I do note that it is around 2.6.22-rc2 timeframe so there is
> a possibility fixes may have gone in since.
>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert@redhat.com>
To: Ian McDonald <ian.mcdonald@jandi.co.nz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
prasanna@in.ibm.com, ananth@in.ibm.com,
anil.s.keshavamurthy@intel.com,
"David S. Miller" <davem@davemloft.net>,
Patrick Andrieux <patrick.andrieux@gmail.com>,
DCCP Mailing List <dccp@vger.kernel.org>
Subject: Re: [BUG] Fwd: segfault : modprobe dccp_probe/tcp_probe
Date: Wed, 06 Jun 2007 18:55:50 -0400 [thread overview]
Message-ID: <46673B76.2090508@redhat.com> (raw)
In-Reply-To: <5640c7e00706061347v42c9ecbahb5354f6687a70a78@mail.gmail.com>
On 06/06/2007 04:47 PM, Ian McDonald wrote:
> Hi there,
>
> We've seen a report of a problem with dccp_probe as shown below. The
> user has also verified that it occurs in tcp_probe as well. This is on
> Dave Miller's tree but that currently tracks Linus' tree quite
> closely. I do note that it is around 2.6.22-rc2 timeframe so there is
> a possibility fixes may have gone in since.
>
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?
next prev parent reply other threads:[~2007-06-06 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 20:47 [BUG] Fwd: segfault : modprobe dccp_probe/tcp_probe Ian McDonald
2007-06-06 20:47 ` Ian McDonald
2007-06-06 22:55 ` Chuck Ebbert [this message]
2007-06-06 22:55 ` Chuck Ebbert
2007-06-06 23:12 ` Ian McDonald
2007-06-06 23:12 ` Ian McDonald
2007-06-07 4:22 ` [PATCH] Kprobes i386 fix for mark ro data S. P. Prasanna
2007-06-07 4:34 ` S. P. Prasanna
2007-06-07 4:24 ` [PATCH] Kprobes x86_64 " S. P. Prasanna
2007-06-07 4:36 ` S. P. Prasanna
2007-06-10 6:24 ` [PATCH] Kprobes i386 " Ian McDonald
2007-06-10 6:24 ` Ian McDonald
2007-06-11 18:36 ` Patrick Andrieux
2007-06-11 18:36 ` Patrick Andrieux
2007-06-07 10:24 ` [BUG] Fwd: segfault : modprobe dccp_probe/tcp_probe Patrick Andrieux
2007-06-07 10:24 ` Patrick Andrieux
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=46673B76.2090508@redhat.com \
--to=cebbert@redhat.com \
--cc=dccp@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.