kernel: not all vnode ops should default to ENOSYS
commit673ccab6ff21d457a175f1258a33689f7d4c4c9e
authorJosef 'Jeff' Sipek <jeffpc@josefsipek.net>
Wed, 21 Jun 2017 05:06:02 +0000 (21 08:06 +0300)
committerJosef 'Jeff' Sipek <jeffpc@josefsipek.net>
Wed, 21 Jun 2017 05:06:02 +0000 (21 08:06 +0300)
tree533aa63d7acdab111816b8f41c0f132022740e41
parent23b01f8b64b8216a112178acdaad57f4ced89561
kernel: not all vnode ops should default to ENOSYS

Some vnode op dispatch functions need to call generic implementations or
return a value different than ENOSYS.  They are:

- vop_setfl needs to return 0
- vop_rwlock needs to return -1
- vop_rwunlock needs to be a no-op
- vop_cmp needs to compare vnode pointers
- vop_frlock needs to call fs_frlock()
- vop_poll needs to call fs_poll()
- vop_pathconf needs to call fs_pathconf()
- vop_dispose needs to call fs_dispose()
- vop_getsecattr needs to call fs_fab_acl()
- vop_shrlock needs to call fs_shrlock()
- vop_vnevent needs to return ENOTSUP
include/sys/vnode_dispatch.h