Actually, IMO, even on 2.4, loosely replacing certain or all
sys_call_table entries are highly discouraged. The reason is
similar...you don't know whether they are currently referenced or not,
right?
Since all other code expects it to be read-only anyway once its setup
(if I'm right),
On Thu, Nov 26, 2009 at 6:31 AM, Fernand LONE SANG flone...@yahoo.com wrote:
As a consequence, I override the permissions to access to the sys_call_table
entries and made them writable using a lkm. After setting the needed
permissions on the page, when I overwrite an entry of the
--- En date de : Jeu 26.11.09, Mulyadi Santosa mulyadi.sant...@gmail.com a
écrit :
De: Mulyadi Santosa mulyadi.sant...@gmail.com
Objet: Re: Overwriting sys_call_table entries
À: flone...@etud.insa-toulouse.fr
Cc: kernelnewbies@nl.linux.org
Date: Jeudi 26 Novembre 2009, 13h51
On Thu, Nov
On 11/27/09, Fernand LONE SANG flone...@etud.insa-toulouse.fr wrote:
I finally found why my lkm froze when i try to change the sys_call_table
entries. Actually, i forgot to change the page directory attributes.
You're right when saying That changing a syscall is discouraged. But for
what i
Hi all,
While playing with kernel data structures, I've been confronted to a huge
mystery : my system freezes. I hope that someone on this mailing list could
help me. For information, i use a 2.6.28 kernel for a x86_64 platform.
These days, I've been trying to set up a kernel module based