From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753798Ab1LWHgv (ORCPT ); Fri, 23 Dec 2011 02:36:51 -0500 Received: from mfb02-md.ns.itscom.net ([175.177.155.110]:51099 "EHLO mfb02-md.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751348Ab1LWHgt (ORCPT ); Fri, 23 Dec 2011 02:36:49 -0500 X-Greylist: delayed 656 seconds by postgrey-1.27 at vger.kernel.org; Fri, 23 Dec 2011 02:36:49 EST From: "J. R. Okajima" Subject: Re: Intercepting system calls To: Gaurav Saxena Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Date: Fri, 23 Dec 2011 16:25:49 +0900 Message-ID: <1162.1324625149@jrobl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Gaurav, Gaurav Saxena: > I am writing an application for which I need to intercept some > filesystem system calls eg. unlink. I need unlink to call my code ::: For kernel space, CONFIG_KPROBES may help you. See Documentation/kprobes.txt in detail. For user space, $LD_PRELOAD may help you. You will need to develop your shared object library which contains your_unlink() and replaces the original unlink(). See ld.so(8) manual page. J. R. Okajima