public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
		systemtap <systemtap@sources.redhat.com>,
		DLE <dle-develop@lists.sourceforge.net>,
		Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH -tip tracing/kprobes 3/6] kprobes/x86: Fix to add 	__kprobes to in-kernel fault handing functions
Date: Sun, 30 Aug 2009 00:54:00 -0000	[thread overview]
Message-ID: <20090830005355.GB387@nowhere> (raw)
In-Reply-To: <20090827172311.8246.92725.stgit@localhost.localdomain>

On Thu, Aug 27, 2009 at 01:23:11PM -0400, Masami Hiramatsu wrote:
> Add __kprobes to the functions which handles in-kernel fixable page faults.
> Since kprobes can cause those in-kernel page faults by accessing kprobe data
> structures, probing those fault functions will cause fault-int3-loop
> (do_page_fault has already been marked as __kprobes).


BTW, is it possible to assert a struct kprobe (and its pointer members)
haven't been allocated through vmalloc() ?

  parent reply	other threads:[~2009-08-30  0:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090827152539.GE6058@nowhere>
2009-08-27 17:21 ` [PATCH -tip tracing/kprobes 1/6] kprobes/x86: Call BUG() when reentering probe into KPROBES_HIT_SS Masami Hiramatsu
2009-08-28  4:39   ` Ananth N Mavinakayanahalli
2009-08-30  1:25   ` Frederic Weisbecker
2009-08-27 17:21 ` [PATCH -tip tracing/kprobes 4/6] kprobes: Fix to add __kprobes to notify_die Masami Hiramatsu
2009-08-28  4:41   ` Ananth N Mavinakayanahalli
2009-08-27 17:21 ` [PATCH -tip tracing/kprobes 3/6] kprobes/x86: Fix to add __kprobes to in-kernel fault handing functions Masami Hiramatsu
2009-08-28  4:41   ` Ananth N Mavinakayanahalli
2009-08-30  0:50   ` Frederic Weisbecker
2009-08-30  2:41     ` Masami Hiramatsu
2009-08-30  0:54   ` Frederic Weisbecker [this message]
2009-08-30  2:48     ` Masami Hiramatsu
2009-08-30 16:10       ` Frederic Weisbecker
2009-08-31  3:59         ` Masami Hiramatsu
2009-09-01 20:05           ` Masami Hiramatsu
2009-09-02 12:56         ` Masami Hiramatsu
2009-09-03  5:46           ` Frederic Weisbecker
2009-09-04 19:07           ` Frederic Weisbecker
2009-09-04 22:26             ` Masami Hiramatsu
2009-09-08 16:31             ` [PATCH tracing/kprobes] x86: Add MMX support for instruction decoder Masami Hiramatsu
2009-09-10 22:57               ` Frederic Weisbecker
2009-09-08 16:53       ` [RFC PATCH tracing/kprobes] kprobes: Call vmalloc_sync_all() for avoiding in-kernel paging on kprobes Masami Hiramatsu
2009-08-27 17:21 ` [PATCH -tip tracing/kprobes 2/6] kprobes/x86-64: Allow to reenter probe on post_handler Masami Hiramatsu
2009-08-28  4:39   ` Ananth N Mavinakayanahalli
2009-08-27 17:22 ` [PATCH -tip tracing/kprobes 6/6] kprobes: Prohibit to probe native_get_debugreg Masami Hiramatsu
2009-08-28  4:41   ` Ananth N Mavinakayanahalli
2009-08-27 17:22 ` [PATCH -tip tracing/kprobes 5/6] kprobes/x86-64: Fix to move common_interrupt to .kprobes.text Masami Hiramatsu

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=20090830005355.GB387@nowhere \
    --to=fweisbec@gmail.com \
    --cc=ananth@in.ibm.com \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=systemtap@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).