All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terje Malmedal <tm@basefarm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Igor Shmukler <igor.shmukler@gmail.com>,
	Rik van Riel <riel@redhat.com>,
	Daniel Souza <thehazard@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: intercepting syscalls
Date: Tue, 19 Apr 2005 10:32:09 +0200	[thread overview]
Message-ID: <wvh8y3fdv5i.fsf@cornavin.basefarm.no> (raw)
In-Reply-To: <1113853203.6274.97.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Mon, 18 Apr 2005 21:40:02 +0200")


[Arjan van de Ven]
>> What do I do the next time I need to do something like this? 

> use kprobes or so to actually replace the faulty lower level function..
> you don't know from how many different angles the lower level function
> is called, so you're really best of by replacing it at the lowest
> possible level, eg closest to the bug. That *very* seldomly is the
> actual syscall function.

This is exactly what I want to do, but how do I do the replacing part?

I understand how I create pre_ and post_handlers with kprobes, but not
how I can stop a function from being executed.

-- 
 - Terje
tm@basefarm.no

  reply	other threads:[~2005-04-19  8:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 18:04 intercepting syscalls Igor Shmukler
2005-04-15 18:11 ` Arjan van de Ven
2005-04-15 19:41   ` Igor Shmukler
2005-04-15 19:51     ` Daniel Souza
2005-04-15 19:59       ` Igor Shmukler
2005-04-15 20:10         ` Daniel Souza
2005-04-15 20:13           ` Arjan van de Ven
2005-04-15 20:19             ` Daniel Souza
2005-04-15 20:25               ` Chris Wright
2005-04-15 20:38               ` Richard B. Johnson
2005-04-15 21:00                 ` Daniel Souza
2005-04-15 20:55         ` Steven Rostedt
2005-04-18 11:54         ` Rik van Riel
2005-04-18 14:48           ` Igor Shmukler
2005-04-18 14:59             ` Arjan van de Ven
2005-04-18 15:06               ` Igor Shmukler
2005-04-18 15:20                 ` Arjan van de Ven
2005-04-18 18:56                   ` Terje Malmedal
2005-04-18 19:19                     ` Timur Tabi
2005-04-18 19:40                     ` Arjan van de Ven
2005-04-19  8:32                       ` Terje Malmedal [this message]
2005-04-18 15:17             ` Randy.Dunlap
2005-04-18 16:20               ` Igor Shmukler
2005-04-18 16:26                 ` Christoph Hellwig
2005-04-15 20:03     ` Randy.Dunlap
2005-04-15 18:12 ` Chris Wright
2005-04-15 18:16 ` Timur Tabi
2005-04-15 19:27 ` Zan Lynx
2005-04-15 20:25 ` Petr Baudis
     [not found] <3TDqB-32g-21@gated-at.bofh.it>
     [not found] ` <3TDAk-38r-23@gated-at.bofh.it>
     [not found]   ` <3TEZl-4eW-23@gated-at.bofh.it>
     [not found]     ` <3TF9b-4lu-25@gated-at.bofh.it>
     [not found]       ` <3TFiG-4Cc-11@gated-at.bofh.it>
     [not found]         ` <3TFsj-4HP-3@gated-at.bofh.it>
     [not found]           ` <3TFsl-4HP-17@gated-at.bofh.it>
     [not found]             ` <3TFC7-4Og-29@gated-at.bofh.it>
     [not found]               ` <3TFVm-50J-5@gated-at.bofh.it>
2005-04-15 23:05                 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>

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=wvh8y3fdv5i.fsf@cornavin.basefarm.no \
    --to=tm@basefarm.com \
    --cc=arjan@infradead.org \
    --cc=igor.shmukler@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=thehazard@gmail.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 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.