/Linux-v5.15/tools/testing/selftests/openat2/ |
D | resolve_test.c | 139 .path = "/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 142 .path = "cheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 145 .path = "abscheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 148 .path = "..", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 151 .path = "../root/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 154 .path = "cheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 157 .path = "abscheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 160 .path = "cheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 163 .path = "abscheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 167 .path = "root", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() [all …]
|
D | rename_attack_test.c | 73 const char *flagname(int resolve) in flagname() argument 75 switch (resolve) { in flagname() 84 void test_rename_attack(int resolve) in test_rename_attack() argument 93 .resolve = resolve, in test_rename_attack() 97 how.resolve = 0; in test_rename_attack() 140 flagname(resolve), ROUNDS, escapes); in test_rename_attack()
|
D | openat2_test.c | 220 .how.resolve = RESOLVE_BENEATH | RESOLVE_IN_ROOT, in test_openat2_flags() 226 .how.resolve = 0x1337, .err = -EINVAL }, in test_openat2_flags() 229 .how.resolve = 0x1337, .err = -EINVAL }, in test_openat2_flags() 232 .how.resolve = 0x1337, .err = -EINVAL }, in test_openat2_flags() 235 .how.resolve = 0x1337, .err = -EINVAL }, in test_openat2_flags() 240 .how.resolve = 0, .err = -EINVAL }, in test_openat2_flags()
|
D | helpers.h | 41 __u64 resolve; member
|
D | helpers.c | 19 return how->resolve != 0; in needs_openat2()
|
/Linux-v5.15/kernel/locking/ |
D | test-ww_mutex.c | 153 bool resolve; member 170 if (abba->resolve && err == -EDEADLK) { in test_abba_work() 184 static int test_abba(bool resolve) in test_abba() argument 195 abba.resolve = resolve; in test_abba() 206 if (resolve && err == -EDEADLK) { in test_abba() 221 if (resolve) { in test_abba()
|
/Linux-v5.15/tools/include/uapi/linux/ |
D | openat2.h | 22 __u64 resolve; member
|
/Linux-v5.15/include/uapi/linux/ |
D | openat2.h | 22 __u64 resolve; member
|
/Linux-v5.15/fs/ |
D | open.c | 1032 if (how->resolve & ~VALID_RESOLVE_FLAGS) in build_open_flags() 1036 if ((how->resolve & RESOLVE_BENEATH) && (how->resolve & RESOLVE_IN_ROOT)) in build_open_flags() 1106 if (how->resolve & RESOLVE_NO_XDEV) in build_open_flags() 1108 if (how->resolve & RESOLVE_NO_MAGICLINKS) in build_open_flags() 1110 if (how->resolve & RESOLVE_NO_SYMLINKS) in build_open_flags() 1112 if (how->resolve & RESOLVE_BENEATH) in build_open_flags() 1114 if (how->resolve & RESOLVE_IN_ROOT) in build_open_flags() 1116 if (how->resolve & RESOLVE_CACHED) { in build_open_flags()
|
/Linux-v5.15/tools/perf/Documentation/ |
D | jit-interface.txt | 1 perf supports a simple JIT interface to resolve symbols for dynamic code generated
|
/Linux-v5.15/net/atm/ |
D | lec.h | 46 int (*resolve) (struct net_device *dev, const u8 *dst_mac, int force, member
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
D | pixfmt-cnf4.rst | 16 unable to resolve any signal and 15 indicating maximum level of confidence for
|
/Linux-v5.15/tools/lib/traceevent/Documentation/ |
D | libtraceevent-func_apis.txt | 27 Some tools may have already a way to resolve the kernel functions. These APIs 40 _tep_find_function_address()_, and _tep_print_func_field()_ to resolve 127 /* These APIs use my_resolve_kernel_addr() to resolve the addr */
|
/Linux-v5.15/Documentation/devicetree/ |
D | dynamic-resolution-notes.rst | 20 2. Adjust all the local phandles of the tree to resolve by that amount.
|
D | overlay-notes.rst | 86 will not be available to resolve the overlay node(s) to the proper location
|
/Linux-v5.15/Documentation/maintainer/ |
D | rebasing-and-merging.rst | 165 maintainer merges with the upstream in order to resolve merge conflicts 179 how you would resolve things. Mention that branch in your pull request, 188 resolve dependencies. These dependency issues do happen at times, and 189 sometimes a cross-merge with another tree is the best way to resolve them; 195 needed. Merging another subsystem tree to resolve a dependency risks
|
/Linux-v5.15/drivers/net/phy/ |
D | phylink.c | 74 struct work_struct resolve; member 656 struct phylink *pl = container_of(w, struct phylink, resolve); in phylink_resolve() 741 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_resolve() 749 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_run_resolve() 758 queue_work(system_power_efficient_wq, &pl->resolve); in phylink_run_resolve_and_disable() 759 flush_work(&pl->resolve); in phylink_run_resolve_and_disable() 827 INIT_WORK(&pl->resolve, phylink_resolve); in phylink_create() 920 cancel_work_sync(&pl->resolve); in phylink_destroy() 1175 flush_work(&pl->resolve); in phylink_disconnect_phy()
|
/Linux-v5.15/Documentation/kbuild/ |
D | Kconfig.recursion-issue-01 | 40 # so trivial to resolve, we provide another example below of practical
|
/Linux-v5.15/Documentation/power/ |
D | drivers-testing.rst | 20 resolve all suspend/resume-related problems in the test system before you start
|
/Linux-v5.15/Documentation/admin-guide/mm/ |
D | userfaultfd.rst | 30 resolve the userfaults it receives via 1) or to manage the virtual 93 ``uffdio_register.ioctls`` bitmask of ioctls that are suitable to resolve 107 There are three basic ways to resolve userfaults: 125 like to do to resolve it:
|
/Linux-v5.15/Documentation/livepatch/ |
D | module-elf-format.rst | 41 since the kernel module loader cannot resolve them and will therefore 46 module Elf output. Using these dynrela sections, livepatch could resolve 238 that the module loader can identify them and not attempt to resolve them.
|
/Linux-v5.15/Documentation/networking/device_drivers/ethernet/intel/ |
D | ixgb.rst | 389 cable assembly may resolve the issue. 395 (1 m or shorter). If this situation occurs, using a longer cable may resolve 401 this situation occurs, using a different cable assembly may resolve the issue. 453 "ethtool -K eth0 tso off" may resolve the problem.
|
/Linux-v5.15/kernel/bpf/ |
D | btf.c | 380 int (*resolve)(struct btf_verifier_env *env, member 2242 .resolve = btf_df_resolve, 2558 .resolve = btf_modifier_resolve, 2567 .resolve = btf_ptr_resolve, 2608 .resolve = btf_df_resolve, 2859 .resolve = btf_array_resolve, 3218 .resolve = btf_struct_resolve, 3386 .resolve = btf_df_resolve, 3464 .resolve = btf_df_resolve, 3507 .resolve = btf_df_resolve, [all …]
|
/Linux-v5.15/drivers/net/wireless/intel/iwlegacy/ |
D | Kconfig | 90 as the debug information can assist others in helping you resolve
|
/Linux-v5.15/Documentation/process/ |
D | kernel-enforcement-statement.rst | 46 failed to resolve the problem.
|