From: Brian Gerst <bgerst@didntduck.org>
To: Harald Barth <haba@pdc.kth.se>, linux-kernel@vger.kernel.org
Subject: Re: Size of pointers in sys_call_table?
Date: Tue, 28 Aug 2001 09:26:24 -0400 [thread overview]
Message-ID: <3B8B9C00.4842710D@didntduck.org> (raw)
In-Reply-To: <20010828145304Z.haba@pdc.kth.se>
Harald Barth wrote:
>
> Most linux kernel ports export the sys_call_table symbol to be used in
> modules. I have not succeeded how to automatially figure out the size
> of a syscall pointer without inspecting the assembler for the
> architecture in question. Examples are mips and sparc64. Have I
> missed a syscall_t type available or shouldn't there be one?
>
> Harald.
The layout of the sys_call_table is totally architecture dependant. The
question to ask here is why do you need to use it? Modifying it to hook
into syscalls is frowned upon.
--
Brian Gerst
next prev parent reply other threads:[~2001-08-28 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 12:53 Size of pointers in sys_call_table? Harald Barth
2001-08-28 13:26 ` Brian Gerst [this message]
2001-08-28 14:30 ` Harald Barth
2001-08-28 16:17 ` Alan Cox
2001-08-29 0:49 ` Keith Owens
2001-08-29 23:26 ` Ralf Baechle
2001-08-30 7:47 ` ioctl conflicts Manik Raina
2001-08-30 8:16 ` Gerd Knorr
2001-08-30 9:31 ` David S. Miller
2001-08-30 9:34 ` Manik Raina
2001-08-30 8:20 ` Alan Cox
2001-08-30 8:30 ` David S. Miller
2001-08-30 9:00 ` Andreas Schwab
2001-08-30 9:14 ` Alan Cox
2001-08-30 9:29 ` David S. Miller
2001-08-30 9:15 ` Andreas Dilger
2001-09-03 1:06 ` Wichert Akkerman
[not found] <3B8B9C00.4842710D@didntduck.org.suse.lists.linux.kernel>
[not found] ` <E15blYK-0006Fb-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-08-28 16:54 ` Size of pointers in sys_call_table? Andi Kleen
2001-08-29 1:00 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B8B9C00.4842710D@didntduck.org \
--to=bgerst@didntduck.org \
--cc=haba@pdc.kth.se \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox