Documentation/bpf/kfuncs.rst

180 2.4.1 KF_ACQUIRE flag
183 The KF_ACQUIRE flag is used to indicate that the kfunc returns a pointer to a
190 2.4.2 KF_RET_NULL flag
193 The KF_RET_NULL flag is used to indicate that the pointer returned by the kfunc
196 another helper). This flag is often used in pairing with KF_ACQUIRE flag, but
199 2.4.3 KF_RELEASE flag
202 The KF_RELEASE flag is used to indicate that the kfunc releases the pointer
205 invoking kfunc with this flag. KF_RELEASE kfuncs automatically receive the
206 protection afforded by the KF_TRUSTED_ARGS flag described below.
208 2.4.4 KF_TRUSTED_ARGS flag
211 The KF_TRUSTED_ARGS flag is used for kfuncs taking pointer arguments. It
273 2.4.5 KF_SLEEPABLE flag
276 The KF_SLEEPABLE flag is used for kfuncs that may sleep. Such kfuncs can only
279 2.4.6 KF_DESTRUCTIVE flag
282 The KF_DESTRUCTIVE flag is used to indicate functions calling which is
288 2.4.7 KF_RCU flag
291 The KF_RCU flag is a weaker version of KF_TRUSTED_ARGS. The kfuncs marked with
301 2.4.8 KF_DEPRECATED flag
304 The KF_DEPRECATED flag is used for kfuncs which are scheduled to be
313 supported and have its KF_DEPRECATED flag removed, it is likely to be far more
314 difficult to remove a KF_DEPRECATED flag after it's been added than it is to
458 KF_DEPRECATED flag to kfunc developers to signal to users that a kfunc has been