| |||||||||||||
Deadlock avoidanceDeadlock avoidancePosted Nov 24, 2004 2:59 UTC (Wed) by brouhaha (subscriber, #1698)Parent article: Should FUSE be merged? Would it be unreasonable to simply expect the program implementing the user-space filesystem to lock itself into memory? If it is unable to do so, perhaps due to lack of locking permission, it could produce a warning to the user or syslog.
(Log in to post comments)
Deadlock avoidance Posted Nov 24, 2004 3:56 UTC (Wed) by elanthis (guest, #6227) [Link] If it is unable to do so, then that means it is not running as root or is untrusted (i.e. not approved of by SELinux or some other security mechanism). If that is the case, you don't want a "warning" - you want to guarantee that it cannot lock the machine. You only want trusted code to even have the possibility of locking up the machine and trusted code would then always have the ability to lock itself into memory, since you trust it.
|
|||||||||||||