On Thu, Jun 24, 2004 at 17:27:48 -0500, Timur Tabi wrote: > I have a driver that needs to call sys_mlock(). This function does Are you sure? The sys_mlock manipulates userspace memory. But a driver does not have any userspace memory to manipulate. It only has kernel memory and that is not swappable. > exactly what I need, which is why I want to call it. However, it > appears that I'm fighting some kind of battle with the kernel > developers. Every time I come up with a technique to find the address > of this function, something changes to break that. I'd really like to > know why. Because that function is a syscall. You should call it as a syscall. But since it only affects userspace memory, the userspace should call it. Really. Could you please tell us what you want to do? It seems quite likely that there is a better solution than trying to call sys_mlock. ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz>
Attachment:
signature.asc
Description: Digital signature
