o Clarify the comments on AIO to note that yes, AIO really is unsuitable
for use on machines with untrusted local users, for security as well as stability reasons. o Lack of clarity pointed out by: David Rufino <dr@soniq.net> via bugtraq.
This commit is contained in:
parent
adbc0684a0
commit
0cbe2ad685
@ -795,8 +795,8 @@ device vcoda 4 #coda minicache <-> venus comm.
|
||||
options EXT2FS
|
||||
|
||||
# Use real implementations of the aio_* system calls. There are numerous
|
||||
# stability issues in the current aio code that make it unsuitable for
|
||||
# inclusion on shell boxes.
|
||||
# stability and security issues in the current aio code that make it
|
||||
# unsuitable for inclusion on machines with untrusted local users.
|
||||
options VFS_AIO
|
||||
|
||||
# Enable the code UFS IO optimization through the VM system. This allows
|
||||
|
@ -795,8 +795,8 @@ device vcoda 4 #coda minicache <-> venus comm.
|
||||
options EXT2FS
|
||||
|
||||
# Use real implementations of the aio_* system calls. There are numerous
|
||||
# stability issues in the current aio code that make it unsuitable for
|
||||
# inclusion on shell boxes.
|
||||
# stability and security issues in the current aio code that make it
|
||||
# unsuitable for inclusion on machines with untrusted local users.
|
||||
options VFS_AIO
|
||||
|
||||
# Enable the code UFS IO optimization through the VM system. This allows
|
||||
|
Loading…
Reference in New Issue
Block a user