Lines Matching refs:hooks

30 general framework that would provide a set of security hooks to control
92 collection of substructures that group related hooks based on the kernel
101 Linus mentioned per-process security hooks in his original remarks as a
102 possible alternative to global security hooks. However, if LSM were to
103 start from the perspective of per-process hooks, then the base framework
107 composing hooks in the base framework. Additionally, LSM would still
108 need global hooks for operations that have no process context (e.g.
110 hooks, but a security module is free to implement per-process hooks
112 process' security field and then invoking these per-process hooks from
113 the global hooks. The problem of composition is thus deferred to the
122 security_ops to the dummy module hooks. This mechanism is used to set
129 :c:func:`unregister_security()` hooks in the :c:type:`struct
132 :c:func:`mod_unreg_security()` functions that invoke these hooks
136 which can implement these hooks in any way it wishes (including always
140 Although the LSM hooks are organized into substructures based on kernel
141 object, all of the hooks can be viewed as falling into two major
142 categories: hooks that are used to manage the security fields and hooks
144 of hooks include the :c:func:`alloc_security()` and
145 :c:func:`free_security()` hooks defined for each kernel data
146 structure that has a security field. These hooks are used to allocate
148 hooks also includes hooks that set information in the security field
152 successful lookup operations. An example of the second category of hooks