Lines Matching refs:hooks
101 to all hooks that operate on a thusly opened object. The <tt>close*()</tt>
103 the cookie might still be in use. Blocking FS hooks (e.g. blocking
134 only hook that specifies a node by ID; all other node-related hooks are
141 There are only four FS hooks through which the VFS gains knowledge of the
150 The remaining two hooks,
159 Which hooks a FS module should provide mainly depends on what functionality
161 queries can omit the respective hooks (i.e. set them to \c NULL in the
162 module, \c fs_volume_ops, and \c fs_vnode_ops structure). Some hooks are
171 most frequently invoked hooks.
205 following hooks:
227 VFS to check access permissions for the other hooks. This has two reasons:
231 The downside is that in most hooks the FS has to check those permissions.
242 function that can be easily reused in other hooks to check the permissions
244 checking to one or two additional "if"s in the hooks where it is required.
303 fs_vnode_ops::write() hooks can then simply be implemented by calling the