Re: Calling sys_mlock() from within a driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 28, 2004 at 09:49:40AM -0500, Timur Tabi wrote:
> Jan Hudec wrote:
> 
> >No. That's wrong. You need to lock_kiobuf, just like direct read and
> >write do.
> 
> The kiobuf functions are now all deprecated - they don't exist in 2.6.
> 
> Besides, what's wrong with sys_mlock()?

A driver should not be making this call.  See the openib-general mailing
list archive for a detailed description on how a driver can avoid making
this call, for one such example of fixing a driver to not do this.

Good luck,

greg k-h

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux