Skip to contentSkip to conversation

why is intercepting system calls considerred bad?

DISCUSSION Bodo Eggert 1 participant 1 message Jul 21, 2006 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 8 lines · Joshua Hudson
Quoted 2 lines · Irfan Habib

I recently met a kernel janitor, who told me that intercepting system calls is undesirable, why?

I'll bite.

You intercept. Somebody else intercepts. You want to stop intercepting.

Use a double-linked list.

Having a mechanism to intercept syscalls will slow down syscall processing, and there was no legit user in the history of linux. If you need something like that, there is ptrace.

Quoted 2 lines

For this reason, anybody who intercepts a system call must be compiled in,

No, but they may need to be compiled in for other reasons.

Quoted 4 lines

and if two intercept the same system call, than the link order dictates behavior.

Obviously not desirable.

ACK.

Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html