Lines Matching full:pointer

74 of the pointer is used. Without __sz annotation, a kfunc cannot accept a void
75 pointer.
93 ID in program's BTF and return a sized pointer to it. Each type ID will have a
135 annotation, the verifier will reject the program if a null pointer is passed in with
205 The KF_ACQUIRE flag is used to indicate that the kfunc returns a pointer to a
206 refcounted object. The verifier will then ensure that the pointer to the object
215 The KF_RET_NULL flag is used to indicate that the pointer returned by the kfunc
216 may be NULL. Hence, it forces the user to do a NULL check on the pointer
224 The KF_RELEASE flag is used to indicate that the kfunc releases the pointer
225 passed in to it. There can be only one referenced pointer that can be passed
226 in. All copies of the pointer being released are invalidated as a result of
233 The KF_TRUSTED_ARGS flag is used for kfuncs taking pointer arguments. It
234 indicates that the all pointer arguments are valid, and that all pointers to
236 offset, and without having been obtained from walking another pointer, with one
250 As mentioned above, a nested pointer obtained from walking a trusted pointer is
253 as its parent pointer is valid, the following macros can be used to express
281 1. Wrap the valid pointer type in a ``BTF_TYPE_SAFE_*`` macro.
318 pointer. Note as well that a KF_ACQUIRE kfunc that is KF_RCU should very likely
369 The verifier will always enforce that the BTF type of a pointer passed to a
370 kfunc by a BPF program, matches the type of pointer specified in the kfunc
526 	 * acquire and release a struct task_struct * pointer.
546 Therefore, when in an RCU read region, you can obtain a pointer to a task
584 caller doesn't have a trusted pointer to a ``struct task_struct *`` object that