Home
last modified time | relevance | path

Searched refs:recursion (Results 1 – 25 of 33) sorted by relevance

12

/Linux-v6.1/kernel/
Dcontext_tracking.c440 int recursion; in context_tracking_recursion_enter() local
442 recursion = __this_cpu_inc_return(context_tracking.recursion); in context_tracking_recursion_enter()
443 if (recursion == 1) in context_tracking_recursion_enter()
446 WARN_ONCE((recursion < 1), "Invalid context tracking recursion value %d\n", recursion); in context_tracking_recursion_enter()
447 __this_cpu_dec(context_tracking.recursion); in context_tracking_recursion_enter()
454 __this_cpu_dec(context_tracking.recursion); in context_tracking_recursion_exit()
Dgen_kheaders.sh88 --owner=0 --group=0 --numeric-owner --no-recursion \
/Linux-v6.1/kernel/events/
Dinternal.h211 static inline int get_recursion_context(int *recursion) in DEFINE_OUTPUT_COPY()
215 if (recursion[rctx]) in DEFINE_OUTPUT_COPY()
218 recursion[rctx]++; in DEFINE_OUTPUT_COPY()
224 static inline void put_recursion_context(int *recursion, int rctx) in put_recursion_context() argument
227 recursion[rctx]--; in put_recursion_context()
/Linux-v6.1/Documentation/kbuild/
Dissues.rst8 .. literalinclude:: Kconfig.recursion-issue-01
14 .. literalinclude:: Kconfig.recursion-issue-02
DKconfig.recursion-issue-016 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
DKconfig.recursion-issue-026 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
Dkconfig-language.rst596 Read: Documentation/kbuild/Kconfig.recursion-issue-01
600 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
605 Read: Documentation/kbuild/Kconfig.recursion-issue-02
609 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
626 Documentation/kbuild/Kconfig.recursion-issue-01 through the removal
632 Documentation/kbuild/Kconfig.recursion-issue-02.
/Linux-v6.1/crypto/
Dalgboss.c106 int recursion = 0; in cryptomgr_schedule_probe() local
112 recursion++; in cryptomgr_schedule_probe()
113 else if (*p == ')' && !recursion--) in cryptomgr_schedule_probe()
/Linux-v6.1/Documentation/trace/
Dfprobe.rst119 Since the recursion safeness of the fprobe (and ftrace) is a bit different
124 handler from recursion in all cases. On the other hand, fprobe uses
128 This is not a matter if the common callback code has its own recursion
129 detection, or it can handle the recursion in the different contexts
131 But if it relies on the 'current_kprobe' recursion lock, it has to check
Dftrace-uses.rst33 There are helper functions to help against recursion, and making sure
116 recursion protection must be used. There are two helper functions that
138 ftrace_test_recursion_trylock() to record where the recursion happened
143 for recursion for the callback and no recursion test needs to be done.
184 By default, it is expected that the callback can handle recursion.
186 setting this bit will add the recursion protection around the
187 callback by calling a helper function that will do the recursion
190 Note, if this flag is not set, and recursion does occur, it could
/Linux-v6.1/tools/testing/selftests/exec/
D.gitignore13 /recursion-depth
DMakefile12 TEST_GEN_PROGS += recursion-depth
/Linux-v6.1/tools/testing/selftests/bpf/prog_tests/
Drecursion.c10 struct recursion *skel; in test_recursion()
/Linux-v6.1/include/linux/
Dcontext_tracking_state.h36 int recursion; member
Dnetdevice.h3132 u16 recursion; member
3181 return this_cpu_read(softnet_data.xmit.recursion); in dev_recursion_level()
3187 return unlikely(__this_cpu_read(softnet_data.xmit.recursion) > in dev_xmit_recursion()
3193 __this_cpu_inc(softnet_data.xmit.recursion); in dev_xmit_recursion_inc()
3198 __this_cpu_dec(softnet_data.xmit.recursion); in dev_xmit_recursion_dec()
/Linux-v6.1/kernel/trace/
DKconfig667 recursion or any unexpected execution path which leads to a kernel
900 of protection against recursion. Even though the protection exists,
903 that triggered a recursion.
905 This will add more overhead to cases that have recursion.
916 the functions that caused a recursion to happen.
926 The ring buffer has its own internal recursion. Although when
927 recursion happens it wont cause harm because of the protection,
929 place where recursion was detected into the ftrace "recursed_functions"
932 This will add more overhead to cases that have recursion.
/Linux-v6.1/security/tomoyo/
Dutil.c437 u8 recursion = 20; in tomoyo_correct_word2() local
474 if (!recursion--) in tomoyo_correct_word2()
/Linux-v6.1/Documentation/core-api/
Dgfp_mask-from-fs-io.rst14 allocating memory to prevent recursion deadlocks caused by direct
Dmemory-allocation.rst74 prevent recursion deadlocks caused by direct memory reclaim calling
/Linux-v6.1/tools/testing/selftests/bpf/
DDENYLIST.s390x32 recursion # skel_attach unexpected error: -524 …
/Linux-v6.1/Documentation/locking/
Dlockdep-design.rst132 referred to as lock recursion deadlock.
141 to lock recursion deadlocks.
316 recursion must not be higher than 20.
/Linux-v6.1/Documentation/crypto/
Dasync-tx-api.rst144 results in recursion in the synchronous case and spin_locks being
/Linux-v6.1/lib/
DKconfig.kcsan52 deadlocks or recursion. If in doubt, say N.
/Linux-v6.1/Documentation/filesystems/
Dlocking.rst612 ops FS recursion Held locks when called
621 FS recursion means calling ->quota_read() and ->quota_write() from superblock
/Linux-v6.1/tools/objtool/
Dcheck.c157 int recursion) in __dead_end_function() argument
237 if (recursion == 5) { in __dead_end_function()
246 return __dead_end_function(file, dest->func, recursion+1); in __dead_end_function()

12