[lkml]   [1999]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: access_ok inside kernelspace
Tigran Aivazian <tigran@sco.COM> said:
> Actually, Ingo - there *is* one case where going through _syscallX() and
> therefore int 0x80 from the kernel *is* the only way. This is when the
> caller is a module. That is how I call sysfs() from BFS module.

I don't understand this. A module is linked into the running kernel, and
has access to all of it AFAIU, so I can't see any need for this contortion
for modules. Maybe I'm just plain blind today...

If it is really needed, some piece of magic should translate them to the
plain calls when they are not modules to get rid of the overhead.
Dr. Horst H. von Brand
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:54    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean