All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Donlan <bdonlan@gmail.com>
To: Oleg Kutkov <elenbert@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intercepting system calls
Date: Thu, 4 Feb 2010 14:26:10 -0500	[thread overview]
Message-ID: <3e8340491002041126l44bb28a7u8f427f0f5c05e57e@mail.gmail.com> (raw)
In-Reply-To: <4B6B193D.4060106@gmail.com>

On Thu, Feb 4, 2010 at 2:00 PM, Oleg Kutkov <elenbert@gmail.com> wrote:
> Hello.
> Maybe this question is often, but all post i found is too old and some
> things is wrong...
> So, i need to intercept some system calls (socket calls) and make my own
> handler.
> Is there legal, correct and clean way to do it, without hacking system call
> table ?
> Thank.

Why do you need to do this? There may be a better way than overriding syscalls.

  reply	other threads:[~2010-02-04 19:26 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 19:00 Intercepting system calls Oleg Kutkov
2010-02-04 19:26 ` Bryan Donlan [this message]
     [not found]   ` <5e9821061002042140le7ba356s48e535c9d8b637ec@mail.gmail.com>
2010-02-05  7:20     ` Bryan Donlan
  -- strict thread matches above, loose matches on Subject: below --
2011-12-22 16:07 Gaurav Saxena
2011-12-22 16:42 ` richard -rw- weinberger
2011-12-22 16:59   ` Gaurav Saxena
2011-12-22 17:05     ` richard -rw- weinberger
2011-12-22 17:16       ` Gaurav Saxena
2011-12-22 17:32         ` richard -rw- weinberger
2011-12-22 17:37           ` Gaurav Saxena
2011-12-22 17:52     ` John Stoffel
2011-12-23  2:22       ` Gaurav Saxena
2011-12-23 14:38         ` John Stoffel
2011-12-23 17:03           ` Gaurav Saxena
2011-12-28 12:56             ` Wojciech Zygmunt Porczyk
2011-12-29  6:38               ` Gaurav Saxena
2011-12-23 14:50       ` Alan Cox
2011-12-23 17:07         ` Gaurav Saxena
2011-12-22 19:03     ` Wakko Warner
2011-12-23  2:25       ` Gaurav Saxena
2011-12-23  9:45       ` Jiri Kosina
2011-12-23 15:10         ` Wakko Warner
2011-12-23  7:25 ` J. R. Okajima
2011-12-23  9:08   ` Gaurav Saxena
2011-12-23  9:16     ` richard -rw- weinberger
2011-12-23  9:22       ` Gaurav Saxena
2011-12-23  9:26         ` richard -rw- weinberger
2011-12-23  9:37           ` Gaurav Saxena
2011-12-23  9:47 ` Jiri Kosina
2011-12-23  9:50   ` Gaurav Saxena
2011-12-23 11:59     ` Gaurav Saxena
2011-12-23 12:29       ` Maxin B John
2011-12-23 12:50         ` Gaurav Saxena
2011-12-23 13:00           ` richard -rw- weinberger
2011-12-24  9:09 ` Gaurav Saxena
2011-12-26  5:53   ` Rajat Sharma
2011-12-28  5:59     ` Gaurav Saxena
2011-12-28 13:44       ` Rajat Sharma
2011-12-29  6:42         ` Gaurav Saxena
2011-12-29  8:49           ` Rajat Sharma
2011-12-29 10:23             ` Gaurav Saxena
2011-12-29 11:11               ` Rajat Sharma
2011-12-29 12:06                 ` Gaurav Saxena
2011-12-29 12:25                   ` Rajat Sharma
2011-12-29 12:32                     ` Gaurav Saxena
     [not found]                       ` <CALJfu6NrF2fjsWUi4gnV9X6AN3rcecL=6=j9ZZADaRGwz3mECw@mail.gmail.com>
2011-12-29 13:12                         ` Rajat Sharma
2011-12-29 14:03                           ` Gaurav Saxena
2011-12-29 14:32                             ` Gaurav Saxena
2012-01-20  7:38                           ` Gaurav Saxena
2011-12-29 14:01                         ` Gaurav Saxena
2004-12-21  4:22 selvakumar nagendran
2004-12-21  4:28 ` Lee Revell
2004-12-21 13:51 ` Steven Rostedt

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=3e8340491002041126l44bb28a7u8f427f0f5c05e57e@mail.gmail.com \
    --to=bdonlan@gmail.com \
    --cc=elenbert@gmail.com \
    --cc=linux-kernel@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.