/linux/kernel/events/ |
H A D | internal.h | 213 static inline int get_recursion_context(u8 *recursion) in DEFINE_OUTPUT_COPY() 217 if (recursion[rctx]) in DEFINE_OUTPUT_COPY() 220 recursion[rctx]++; in DEFINE_OUTPUT_COPY() 226 static inline void put_recursion_context(u8 *recursion, unsigned char rctx) in put_recursion_context() argument 229 recursion[rctx]--; in put_recursion_context()
|
/linux/net/core/ |
H A D | dev.h | 345 return unlikely(__this_cpu_read(softnet_data.xmit.recursion) > in dev_xmit_recursion() 351 __this_cpu_inc(softnet_data.xmit.recursion); in dev_xmit_recursion_inc() 356 __this_cpu_dec(softnet_data.xmit.recursion); in dev_xmit_recursion_dec() 361 return unlikely(current->net_xmit.recursion > XMIT_RECURSION_LIMIT); 366 current->net_xmit.recursion++; 371 current->net_xmit.recursion--;
|
/linux/Documentation/kbuild/ |
H A D | issues.rst | 8 .. literalinclude:: Kconfig.recursion-issue-01 14 .. literalinclude:: Kconfig.recursion-issue-02
|
H A D | Kconfig.recursion-issue-01 | 6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig 36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
|
H A D | Kconfig.recursion-issue-02 | 6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig 23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
|
/linux/Documentation/trace/ |
H A D | ftrace-uses.rst | 33 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
|
H A D | fprobe.rst | 143 Since the recursion safeness of the fprobe (and ftrace) is a bit different 148 handler from recursion in all cases. On the other hand, fprobe uses 152 This is not a matter if the common callback code has its own recursion 153 detection, or it can handle the recursion in the different contexts 155 But if it relies on the 'current_kprobe' recursion lock, it has to check
|
/linux/include/linux/ |
H A D | netdevice_xmit.h | 6 u16 recursion; member
|
H A D | context_tracking_state.h | 36 int recursion; member
|
H A D | netdevice.h | 3520 return this_cpu_read(softnet_data.xmit.recursion); in dev_recursion_level() 3525 return current->net_xmit.recursion; in dev_recursion_level()
|
/linux/tools/testing/selftests/exec/ |
H A D | .gitignore | 17 /recursion-depth
|
H A D | Makefile | 20 TEST_GEN_PROGS += recursion-depth
|
/linux/tools/testing/selftests/bpf/prog_tests/ |
H A D | recursion.c | 10 struct recursion *skel; in test_recursion()
|
/linux/kernel/trace/ |
H A D | Kconfig | 755 recursion or any unexpected execution path which leads to a kernel 988 of protection against recursion. Even though the protection exists, 991 that triggered a recursion. 993 This will add more overhead to cases that have recursion. 1004 the functions that caused a recursion to happen. 1014 protection against recursion. This option is only to verify that 1027 The ring buffer has its own internal recursion. Although when 1028 recursion happens it won't cause harm because of the protection, 1030 place where recursion was detected into the ftrace "recursed_functions" 1033 This will add more overhead to cases that have recursion.
|
/linux/security/tomoyo/ |
H A D | util.c | 437 u8 recursion = 20; in tomoyo_correct_word2() local 474 if (!recursion--) in tomoyo_correct_word2()
|
/linux/arch/um/drivers/ |
H A D | Kconfig | 170 # in theory, just VIRTIO is enough, but that causes recursion
|
/linux/Documentation/locking/ |
H A D | lockdep-design.rst | 132 referred to as lock recursion deadlock. 141 to lock recursion deadlocks. 316 recursion must not be higher than 20.
|
/linux/Documentation/crypto/ |
H A D | async-tx-api.rst | 144 results in recursion in the synchronous case and spin_locks being
|
/linux/Documentation/core-api/ |
H A D | memory-allocation.rst | 75 prevent recursion deadlocks caused by direct memory reclaim calling
|
/linux/lib/ |
H A D | Kconfig.kcsan | 53 deadlocks or recursion. If in doubt, say N.
|
/linux/tools/objtool/ |
H A D | check.c | 248 int recursion) in __dead_end_function() argument 306 if (recursion == 5) { in __dead_end_function() 315 return __dead_end_function(file, insn_func(dest), recursion+1); in __dead_end_function()
|
/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 1510 recursion, either the control variable will overflow or (in the Linux 1996 to result in destructive recursion via interrupt handler's use of RCU. 2003 by tracing, which avoids the destructive recursion that could otherwise
|
/linux/Documentation/security/keys/ |
H A D | core.rst | 625 checked for keys before recursion into its children occurs.
|