Skip to contentSkip to conversation

ATI modules using the _syscall() macro for unexported syscalls (was: Re: Fw: Re: [patch 02/11] uml: fix compilation for missing headers)

DISCUSSION Blaisorblade 1 participant 1 message Feb 3, 2005 3 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]

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

#3 lore raw
Quoted 1 line · Andrew Morton

David Howells <[email protected]> wrote:

[....]

Quoted 3 lines

I'm not sure that we even use errno any more. The only syscall trap which the kernel internally takes now is execve(). Everything else is (or should be) just calling the sys_foo() function directly.

The ATI kernel modules reportedly use the syscall() facility to call modify_ldt, which I guess is not exported... I've received the report of this because that causes a name conflict with the SKAS patch I maintain.

Also, I have the doubt is that they're circumventing EXPORT_SYMBOL restrictions and thus violating the license. IANAL, however.

Signature · 3 lines
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade