Prev: [PATCH] tty: fix obsolete comment on tty_insert_flip_string_fixed_flag
Next: eeepc-wmi: depends on BACKLIGHT_CLASS_DEVICE
From: Leonidas . on 7 May 2010 14:00
Hi folks,

Is it possible to wrap module entry points like open/close during the
module compilation?
By wrapping, I mean interposing using linker --wrap option. This is
very much possible in
user space and is commonly used to interpose library functions.

E.g.

void *
__wrap_malloc (int c)
{
printf ("malloc called with %ld\n", c);
return __real_malloc (c);
}

int main()
{
malloc(17);
return 0;
}

Above works expected, can we wrap kmalloc this way?

-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Leonidas . on 9 May 2010 03:00
Couple more questions:

1. How does the dynamic linking/loading happen in kernel? What is the
equivalent of ld-linux.so in kernel space?

Any pointer will be helpful

-Leo

On Fri, May 7, 2010 at 11:21 PM, Leonidas . <leonidas137(a)gmail.com> wrote:
> Hi folks,
>
> Is it possible to wrap module entry points like open/close during the
> module compilation?
> By wrapping, I mean interposing using linker --wrap option. This is
> very much possible in
> user space and is commonly used to interpose library functions.
>
> E.g.
>
> void *
> __wrap_malloc (int c)
> {
> �printf ("malloc called with %ld\n", c);
> �return __real_malloc (c);
> }
>
> int main()
> {
> � �malloc(17);
> � �return 0;
> }
>
> Above works expected, can we wrap kmalloc this way?
>
> -Leo.
>



--


-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Arjan van de Ven on 9 May 2010 10:40
On Sun, 9 May 2010 12:21:35 +0530
"Leonidas ." <leonidas137(a)gmail.com> wrote:

> Couple more questions:
>
> 1. How does the dynamic linking/loading happen in kernel? What is the
> equivalent of ld-linux.so in kernel space?

lkml is not rootkit-help-for-free ;-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Leonidas . on 9 May 2010 11:20
>
> lkml is not rootkit-help-for-free ;-)

I promise that I am not going to write a root kit :-). But you gave me
a good start, I will
have to check some of the root kits in order to see how things happen there.

Actually, I want to see similarities between user space way of
linking/loading compared to
kernel space. Have not been able to figure out completely yet at
conceptual level. I have
gone through module.c file and insmod utility.

Any pointers to earlier such attempts would be helpful.

-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] tty: fix obsolete comment on tty_insert_flip_string_fixed_flag
Next: eeepc-wmi: depends on BACKLIGHT_CLASS_DEVICE