Searched refs:kptr_restrict (Results 1 – 12 of 12) sorted by relevance
22 * kernel profiling and are explicitly not paranoid (so kptr_restrict25 * Otherwise, require CAP_SYSLOG (assuming kptr_restrict isn't set to30 switch (kptr_restrict) { in kallsyms_show_value()
31 kptr_restrict, member
1019 if (symbol_conf.kptr_restrict) { in symbol__restricted_filename() 2450 FILE *fp = fopen("/proc/sys/kernel/kptr_restrict", "r"); in symbol__read_kptr_restrict() 2579 symbol_conf.kptr_restrict = symbol__read_kptr_restrict(); in symbol__init()
388 extern int kptr_restrict;
551 kptr_restrict chapter 557 When ``kptr_restrict`` is set to 0 (the default) the address is hashed561 When ``kptr_restrict`` is set to 1, kernel pointers printed using the576 When ``kptr_restrict`` is set to 2, kernel pointers printed using
306 - /proc/sys/kernel/kptr_restrict = 2 (restrict all users) also prevents perf probe to retrieve the important information from kallsyms. You also need to set to 1 (restrict non CAP_SYSLOG users) for the above commands. Since the user-space probe doesn't need to access kallsyms, this is only for probing the kernel function (kprobes).
857 int kptr_restrict __read_mostly;863 switch (kptr_restrict) { in restricted_pointer() 871 * kptr_restrict==1 cannot be used in IRQ context in restricted_pointer()
163 users. The behaviour of %pK depends on the kptr_restrict sysctl - see
785 symbol_conf.kptr_restrict && in perf_event__process_sample() 790 "Check /proc/sys/kernel/kptr_restrict and /proc/sys/kernel/perf_event_paranoid.\n\n" in perf_event__process_sample()
1415 if (symbol_conf.kptr_restrict && !evlist__exclude_kernel(evlist)) { in record__open() 1418 "check /proc/sys/kernel/kptr_restrict and /proc/sys/kernel/perf_event_paranoid.\n\n" in record__open()
1970 if (symbol_conf.kptr_restrict) { in trace__machine__resolve_kernel_addr() 1972 "Check /proc/sys/kernel/kptr_restrict and /proc/sys/kernel/perf_event_paranoid.\n\n" in trace__machine__resolve_kernel_addr()