Messages in this thread | | | Subject | Re: access_ok inside kernelspace | Date | Tue, 19 Oct 1999 09:18:41 -0300 | From | Horst von Brand <> |
| |
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 mailto:vonbrand@inf.utfsm.cl 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 majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |