CVSROOT: /cvs
Module name: www
Changes by: [email protected] 2020/05/06 23:38:28
Modified files:
. : 67.html
Log message:
Prefer 'without KERNEL_LOCK' as 'unlocking' for system calls.
Most (all?) the systems calls do run with locks, the 'NOLOCK' keyword used
by kern/syscall.master and the 'unlocking' expression can be misleading.
The ioctl(2) syscall is still mostly run under KERNEL_LOCK, even if an entry
is marked as 'NOLOCK' in kern/syscall.master it doesn't mean it is free from
it. In this case, like for read(2) and write(2) the KERNEL_LOCK is taken at
the `fileops' layer (vn_ioctl(), vn_read(), etc).
Remove unrelated refactoring.
Prodded by benno@
