mirror of
https://git.openafs.org/openafs.git
synced 2025-01-18 15:00:12 +00:00
407eadbcd7
FreeBSD commit 6fa079fc3f5e7e120f166420c6f0c60f701ba9ae (vfs: flatten vop vectors) changed how the .vop_default field in struct vop_vector works. Previously, we just set .vop_default to a default set of function pointers (default_vnodeops), and any caller would use that if any of our function pointers were NULL. After commit 6fa079fc3f, instead all declared struct vop_vector's must call vfs_vector_op_register(), which merges the .vop_default contents into the main struct vop_vector, and so callers can call the needed function pointer unconditionally. Most filesystems use VFS_VOP_VECTOR_REGISTER() to do this, which arranges for vfs_vector_op_register() to be called on boot or module load. If we don't call vfs_vector_op_register(), then we get a kernel panic when mounting AFS, since various vnode ops are NULL (such as vop_lock1). So to fix this, call VFS_VOP_VECTOR_REGISTER() when available. Change-Id: I6137e3ed0b21fbda5c3d3df300dfe9ae4cb3925d Reviewed-on: https://gerrit.openafs.org/15173 Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> Reviewed-by: Andrew Deason <adeason@sinenomine.net> Tested-by: BuildBot <buildbot@rampaginggeek.com> |
||
|---|---|---|
| build-tools | ||
| doc | ||
| src | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .splintrc | ||
| acinclude.m4 | ||
| CODING | ||
| configure-libafs.ac | ||
| configure.ac | ||
| CONTRIBUTING | ||
| INSTALL | ||
| libafsdep | ||
| LICENSE | ||
| Makefile-libafs.in | ||
| Makefile.in | ||
| NEWS | ||
| NTMakefile | ||
| README | ||
| README-WINDOWS | ||
| regen.sh | ||
AFS is a distributed file system that enables users to share and access all of the files stored in a network of computers as easily as they access the files stored on their local machines. The file system is called distributed for this exact reason: files can reside on many different machines, but are available to users on every machine. OpenAFS 1.0 was originally released by IBM under the terms of the IBM Public License 1.0 (IPL10). For details on IPL10 see the LICENSE file in this directory. The current OpenAFS distribution is licensed under a combination of the IPL10 and many other licenses as granted by the relevant copyright holders. The LICENSE file in this directory contains more details, thought it is not a comprehensive statement. See INSTALL for information about building and installing OpenAFS on various platforms. See CODING for developer information and guidelines. See NEWS for recent changes to OpenAFS.