linux-kernel - Re: Link time manipulation of kernel symbols like read/write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <j2if22d86811005082351x975e868foe1b40bf7a89e1448@mail.gmail.com>
Date:	Sun, 9 May 2010 12:21:35 +0530
From:	"Leonidas ." <leonidas137@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Link time manipulation of kernel symbols like read/write

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@...il.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/