From mboxrd@z Thu Jan  1 00:00:00 1970
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
Date: Mon, 26 Mar 2012 15:27:49 +0700
Subject: Hooking a system call.
In-Reply-To: <CA+CftcGKroq9U2CU6YwQGGFRhd6s99-AhpGmz9JTm+C=VkuhVw@mail.gmail.com>
References: <CA+CftcHQhzN2apM5hrrgN=_gZSZjL3znqdLx6YhT6TJksM3V1Q@mail.gmail.com>
	<CAGdaadaJerz7PgXt-tzJmpPoK6MdefQVRXxzPyYV_2Q=ffmQ8Q@mail.gmail.com>
	<CA+CftcGKroq9U2CU6YwQGGFRhd6s99-AhpGmz9JTm+C=VkuhVw@mail.gmail.com>
Message-ID: <CAGdaadZTEXP_y65HqFvpx_fmhoeUm8g9bRi_aBzVRANAW_LjSw@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, Mar 26, 2012 at 15:14, V.Ravikumar <ravikumar.vallabhu@gmail.com> wrote:
> But in my sample module example code for? intercepting system call. how can
> I make system_call_table address to writable so that one can change to
> customized system call.

My memory is a bit rigid about this part, but IIRC it's work of linker
script that put the section that holds syscall table into read-only
section. Not sure if that attribute could be changed on the fly

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com