sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget-/translations/zh_CN/admin-guide/perf-securitymodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/zh_TW/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/it_IT/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/ja_JP/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/ko_KR/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/pt_BR/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget-/translations/sp_SP/admin-guide/perf-securitymodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhtarget)}(h.. _perf_security:h]h}(h]h ]h"]h$]h&]refid perf-securityuh1hhKhhhhhG/var/lib/git/docbuild/linux/Documentation/admin-guide/perf-security.rstubhsection)}(hhh](htitle)}(hPerf events and tool securityh]hPerf events and tool security}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hOverviewh]hOverview}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hX9Usage of Performance Counters for Linux (perf_events) [1]_ , [2]_ , [3]_ can impose a considerable risk of leaking sensitive data accessed by monitored processes. The data leakage is possible both in scenarios of direct usage of perf_events system call API [2]_ and over data files generated by Perf tool user mode utility (Perf) [3]_ , [4]_ . The risk depends on the nature of data that perf_events performance monitoring units (PMU) [2]_ and Perf collect and expose for performance analysis. Collected system and performance data may be split into several categories:h](h6Usage of Performance Counters for Linux (perf_events) }(hhhhhNhNubhfootnote_reference)}(h[1]_h]h1}(hhhhhNhNubah}(h]id1ah ]h"]h$]h&]hid32docnameadmin-guide/perf-securityuh1hhhresolvedKubh , }(hhhhhNhNubh)}(h[2]_h]h2}(hj hhhNhNubah}(h]id2ah ]h"]h$]h&]hid33jjuh1hhhjKubh , }hhsbh)}(h[3]_h]h3}(hj!hhhNhNubah}(h]id3ah ]h"]h$]h&]hid34jjuh1hhhjKubh can impose a considerable risk of leaking sensitive data accessed by monitored processes. The data leakage is possible both in scenarios of direct usage of perf_events system call API }(hhhhhNhNubh)}(h[2]_h]h2}(hj5hhhNhNubah}(h]id4ah ]h"]h$]h&]hjjjuh1hhhjKubhE and over data files generated by Perf tool user mode utility (Perf) }(hhhhhNhNubh)}(h[3]_h]h3}(hjHhhhNhNubah}(h]id5ah ]h"]h$]h&]hj0jjuh1hhhjKubh , }hhsbh)}(h[4]_h]h4}(hj[hhhNhNubah}(h]id6ah ]h"]h$]h&]hid35jjuh1hhhjKubh^ . The risk depends on the nature of data that perf_events performance monitoring units (PMU) }(hhhhhNhNubh)}(h[2]_h]h2}(hjohhhNhNubah}(h]id7ah ]h"]h$]h&]hjjjuh1hhhjKubh and Perf collect and expose for performance analysis. Collected system and performance data may be split into several categories:}(hhhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK hhhhubhenumerated_list)}(hhh](h list_item)}(hX'System hardware and software configuration data, for example: a CPU model and its cache configuration, an amount of available memory and its topology, used kernel and Perf versions, performance monitoring setup including experiment time, events configuration, Perf command line parameters, etc. h]h)}(hX&System hardware and software configuration data, for example: a CPU model and its cache configuration, an amount of available memory and its topology, used kernel and Perf versions, performance monitoring setup including experiment time, events configuration, Perf command line parameters, etc.h]hX&System hardware and software configuration data, for example: a CPU model and its cache configuration, an amount of available memory and its topology, used kernel and Perf versions, performance monitoring setup including experiment time, events configuration, Perf command line parameters, etc.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubj)}(hUser and kernel module paths and their load addresses with sizes, process and thread names with their PIDs and TIDs, timestamps for captured hardware and software events. h]h)}(hUser and kernel module paths and their load addresses with sizes, process and thread names with their PIDs and TIDs, timestamps for captured hardware and software events.h]hUser and kernel module paths and their load addresses with sizes, process and thread names with their PIDs and TIDs, timestamps for captured hardware and software events.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubj)}(hXContent of kernel software counters (e.g., for context switches, page faults, CPU migrations), architectural hardware performance counters (PMC) [8]_ and machine specific registers (MSR) [9]_ that provide execution metrics for various monitored parts of the system (e.g., memory controller (IMC), interconnect (QPI/UPI) or peripheral (PCIe) uncore counters) without direct attribution to any execution context state. h]h)}(hXContent of kernel software counters (e.g., for context switches, page faults, CPU migrations), architectural hardware performance counters (PMC) [8]_ and machine specific registers (MSR) [9]_ that provide execution metrics for various monitored parts of the system (e.g., memory controller (IMC), interconnect (QPI/UPI) or peripheral (PCIe) uncore counters) without direct attribution to any execution context state.h](hContent of kernel software counters (e.g., for context switches, page faults, CPU migrations), architectural hardware performance counters (PMC) }(hjhhhNhNubh)}(h[8]_h]h8}(hjhhhNhNubah}(h]id8ah ]h"]h$]h&]hid39jjuh1hhjjKubh& and machine specific registers (MSR) }(hjhhhNhNubh)}(h[9]_h]h9}(hjhhhNhNubah}(h]id9ah ]h"]h$]h&]hid40jjuh1hhjjKubh that provide execution metrics for various monitored parts of the system (e.g., memory controller (IMC), interconnect (QPI/UPI) or peripheral (PCIe) uncore counters) without direct attribution to any execution context state.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubj)}(hContent of architectural execution context registers (e.g., RIP, RSP, RBP on x86_64), process user and kernel space memory addresses and data, content of various architectural MSRs that capture data from this category. h]h)}(hContent of architectural execution context registers (e.g., RIP, RSP, RBP on x86_64), process user and kernel space memory addresses and data, content of various architectural MSRs that capture data from this category.h]hContent of architectural execution context registers (e.g., RIP, RSP, RBP on x86_64), process user and kernel space memory addresses and data, content of various architectural MSRs that capture data from this category.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK%hjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubeh}(h]h ]h"]h$]h&]enumtypearabicprefixhsuffix.uh1jhhhhhhhKubh)}(hXData that belong to the fourth category can potentially contain sensitive process data. If PMUs in some monitoring modes capture values of execution context registers or data from process memory then access to such monitoring modes requires to be ordered and secured properly. So, perf_events performance monitoring and observability operations are the subject for security access control management [5]_ .h](hXData that belong to the fourth category can potentially contain sensitive process data. If PMUs in some monitoring modes capture values of execution context registers or data from process memory then access to such monitoring modes requires to be ordered and secured properly. So, perf_events performance monitoring and observability operations are the subject for security access control management }(hj"hhhNhNubh)}(h[5]_h]h5}(hj*hhhNhNubah}(h]id10ah ]h"]h$]h&]hid36jjuh1hhj"jKubh .}(hj"hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK*hhhhubeh}(h]overviewah ]h"]overviewah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hperf_events access controlh]hperf_events access control}(hjOhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjLhhhhhK2ubh)}(hXTo perform security checks, the Linux implementation splits processes into two categories [6]_ : a) privileged processes (whose effective user ID is 0, referred to as superuser or root), and b) unprivileged processes (whose effective UID is nonzero). Privileged processes bypass all kernel security permission checks so perf_events performance monitoring is fully available to privileged processes without access, scope and resource restrictions.h](hZTo perform security checks, the Linux implementation splits processes into two categories }(hj]hhhNhNubh)}(h[6]_h]h6}(hjehhhNhNubah}(h]id11ah ]h"]h$]h&]hid37jjuh1hhj]jKubhX` : a) privileged processes (whose effective user ID is 0, referred to as superuser or root), and b) unprivileged processes (whose effective UID is nonzero). Privileged processes bypass all kernel security permission checks so perf_events performance monitoring is fully available to privileged processes without access, scope and resource restrictions.}(hj]hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK4hjLhhubh)}(hUnprivileged processes are subject to a full security permission check based on the process's credentials [5]_ (usually: effective UID, effective GID, and supplementary group list).h](hlUnprivileged processes are subject to a full security permission check based on the process’s credentials }(hjhhhNhNubh)}(h[5]_h]h5}(hjhhhNhNubah}(h]id12ah ]h"]h$]h&]hj9jjuh1hhjjKubhG (usually: effective UID, effective GID, and supplementary group list).}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK=0: *scope* includes per-process and system wide performance monitoring but excludes raw tracepoints and ftrace function tracepoints monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK [6]_ capability. h](j)}(h>=0:h]h>=0:}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjgubj)}(hhh]h)}(hX*scope* includes per-process and system wide performance monitoring but excludes raw tracepoints and ftrace function tracepoints monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK [6]_ capability.h](j)}(h*scope*h]hscope}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj|ubhX includes per-process and system wide performance monitoring but excludes raw tracepoints and ftrace function tracepoints monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK }(hj|hhhNhNubh)}(h[6]_h]h6}(hjhhhNhNubah}(h]id26ah ]h"]h$]h&]hjtjjuh1hhj|jKubh capability.}(hj|hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjyubah}(h]h ]h"]h$]h&]uh1jhjgubeh}(h]h ]h"]h$]h&]uh1jhhhKhjhhubj)}(hXt>=1: *scope* includes per-process performance monitoring only and excludes system wide performance monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability. h](j)}(h>=1:h]h>=1:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(hXn*scope* includes per-process performance monitoring only and excludes system wide performance monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability.h](j)}(h*scope*h]hscope}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhXg includes per-process performance monitoring only and excludes system wide performance monitoring. CPU and system events happened when executing either in user or in kernel space can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjhhubj)}(hX5>=2: *scope* includes per-process performance monitoring only. CPU and system events happened when executing in user space only can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability. h](j)}(h>=2:h]h>=2:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(hX/*scope* includes per-process performance monitoring only. CPU and system events happened when executing in user space only can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability.h](j)}(h*scope*h]hscope}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubhX( includes per-process performance monitoring only. CPU and system events happened when executing in user space only can be monitored and captured for later analysis. Per-user per-cpu perf_event_mlock_kb locking limit is imposed but ignored for unprivileged processes with CAP_IPC_LOCK capability.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubeh}(h]h ]h"]h$]h&]uh1jhj|hhhhhNubeh}(h]unprivileged-usersah ]h"]unprivileged usersah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hResource controlh]hResource control}(hjBhhhNhNubah}(h]h ]h"]h$]h&]uh1hhj?hhhhhMubh)}(hhh](h)}(hOpen file descriptorsh]hOpen file descriptors}(hjShhhNhNubah}(h]h ]h"]h$]h&]uh1hhjPhhhhhM ubh)}(hXThe perf_events system call API [2]_ allocates file descriptors for every configured PMU event. Open file descriptors are a per-process accountable resource governed by the RLIMIT_NOFILE [11]_ limit (ulimit -n), which is usually derived from the login shell process. When configuring Perf collection for a long list of events on a large server system, this limit can be easily hit preventing required monitoring configuration. RLIMIT_NOFILE limit can be increased on per-user basis modifying content of the limits.conf file [12]_ . Ordinarily, a Perf sampling session (perf record) requires an amount of open perf_event file descriptors that is not less than the number of monitored events multiplied by the number of monitored CPUs.h](h The perf_events system call API }(hjahhhNhNubh)}(h[2]_h]h2}(hjihhhNhNubah}(h]id27ah ]h"]h$]h&]hjjjuh1hhjajKubh allocates file descriptors for every configured PMU event. Open file descriptors are a per-process accountable resource governed by the RLIMIT_NOFILE }(hjahhhNhNubh)}(h[11]_h]h11}(hj|hhhNhNubah}(h]id28ah ]h"]h$]h&]hid42jjuh1hhjajKubhXL limit (ulimit -n), which is usually derived from the login shell process. When configuring Perf collection for a long list of events on a large server system, this limit can be easily hit preventing required monitoring configuration. RLIMIT_NOFILE limit can be increased on per-user basis modifying content of the limits.conf file }(hjahhhNhNubh)}(h[12]_h]h12}(hjhhhNhNubah}(h]id29ah ]h"]h$]h&]hid43jjuh1hhjajKubh . Ordinarily, a Perf sampling session (perf record) requires an amount of open perf_event file descriptors that is not less than the number of monitored events multiplied by the number of monitored CPUs.}(hjahhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM hjPhhubeh}(h]open-file-descriptorsah ]h"]open file descriptorsah$]h&]uh1hhj?hhhhhM ubh)}(hhh](h)}(hMemory allocationh]hMemory allocation}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hXThe amount of memory available to user processes for capturing performance monitoring data is governed by the perf_event_mlock_kb [2]_ setting. This perf_event specific resource setting defines overall per-cpu limits of memory allowed for mapping by the user processes to execute performance monitoring. The setting essentially extends the RLIMIT_MEMLOCK [11]_ limit, but only for memory regions mapped specifically for capturing monitored performance events and related data.h](hThe amount of memory available to user processes for capturing performance monitoring data is governed by the perf_event_mlock_kb }(hjhhhNhNubh)}(h[2]_h]h2}(hjhhhNhNubah}(h]id30ah ]h"]h$]h&]hjjjuh1hhjjKubh setting. This perf_event specific resource setting defines overall per-cpu limits of memory allowed for mapping by the user processes to execute performance monitoring. The setting essentially extends the RLIMIT_MEMLOCK }(hjhhhNhNubh)}(h[11]_h]h11}(hjhhhNhNubah}(h]id31ah ]h"]h$]h&]hjjjuh1hhjjKubht limit, but only for memory regions mapped specifically for capturing monitored performance events and related data.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXFor example, if a machine has eight cores and perf_event_mlock_kb limit is set to 516 KiB, then a user process is provided with 516 KiB * 8 = 4128 KiB of memory above the RLIMIT_MEMLOCK limit (ulimit -l) for perf_event mmap buffers. In particular, this means that, if the user wants to start two or more performance monitoring processes, the user is required to manually distribute the available 4128 KiB between the monitoring processes, for example, using the --mmap-pages Perf record mode option. Otherwise, the first started performance monitoring process allocates all available 4128 KiB and the other processes will fail to proceed due to the lack of memory.h]hXFor example, if a machine has eight cores and perf_event_mlock_kb limit is set to 516 KiB, then a user process is provided with 516 KiB * 8 = 4128 KiB of memory above the RLIMIT_MEMLOCK limit (ulimit -l) for perf_event mmap buffers. In particular, this means that, if the user wants to start two or more performance monitoring processes, the user is required to manually distribute the available 4128 KiB between the monitoring processes, for example, using the --mmap-pages Perf record mode option. Otherwise, the first started performance monitoring process allocates all available 4128 KiB and the other processes will fail to proceed due to the lack of memory.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM"hjhhubh)}(hXDRLIMIT_MEMLOCK and perf_event_mlock_kb resource constraints are ignored for processes with the CAP_IPC_LOCK capability. Thus, perf_events/Perf privileged users can be provided with memory above the constraints for perf_events/Perf performance monitoring purpose by providing the Perf executable with CAP_IPC_LOCK capability.h]hXDRLIMIT_MEMLOCK and perf_event_mlock_kb resource constraints are ignored for processes with the CAP_IPC_LOCK capability. Thus, perf_events/Perf privileged users can be provided with memory above the constraints for perf_events/Perf performance monitoring purpose by providing the Perf executable with CAP_IPC_LOCK capability.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM-hjhhubeh}(h]memory-allocationah ]h"]memory allocationah$]h&]uh1hhj?hhhhhMubeh}(h]resource-controlah ]h"]resource controlah$]h&]uh1hhhhhhhhMubh)}(hhh](h)}(h Bibliographyh]h Bibliography}(hj&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj#hhhhhM4ubhfootnote)}(h%``_h](hlabel)}(h1h]h1}(hj<hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj6ubh)}(hj8h](h reference)}(hj8h]h https://lwn.net/Articles/337493/}(hjOhhhNhNubah}(h]h ]h"]h$]h&]name https://lwn.net/Articles/337493/refurij]uh1jMhjJubh)}(h"h]h}(h]https-lwn-net-articles-337493ah ]h"] https://lwn.net/articles/337493/ah$]h&]refurij]uh1h referencedKhjJubeh}(h]h ]h"]h$]h&]uh1hhhhM6hj6ubeh}(h]jah ]h"]1ah$]h&]jajjuh1j4hhhM6hj#hhjKubj5)}(h@``_h](j;)}(h2h]h2}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjzubh)}(hj|h](jN)}(hj|h]h;http://man7.org/linux/man-pages/man2/perf_event_open.2.html}(hjhhhNhNubah}(h]h ]h"]h$]h&]name;http://man7.org/linux/man-pages/man2/perf_event_open.2.htmlj^juh1jMhjubh)}(h=h]h}(h]9http-man7-org-linux-man-pages-man2-perf-event-open-2-htmlah ]h"];http://man7.org/linux/man-pages/man2/perf_event_open.2.htmlah$]h&]refurijuh1hjlKhjubeh}(h]h ]h"]h$]h&]uh1hhhhM7hjzubeh}(h]jah ]h"]2ah$]h&](jj?jyjj(jsjejjuh1j4hhhM7hj#hhjKubj5)}(h=``_h](j;)}(h3h]h3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjubh)}(hjh](jN)}(hjh]h8http://web.eece.maine.edu/~vweaver/projects/perf_events/}(hjhhhNhNubah}(h]h ]h"]h$]h&]name8http://web.eece.maine.edu/~vweaver/projects/perf_events/j^juh1jMhjubh)}(h:h]h}(h]4http-web-eece-maine-edu-vweaver-projects-perf-eventsah ]h"]8http://web.eece.maine.edu/~vweaver/projects/perf_events/ah$]h&]refurijuh1hjlKhjubeh}(h]h ]h"]h$]h&]uh1hhhhM8hjubeh}(h]j0ah ]h"]3ah$]h&](j+jRejjuh1j4hhhM8hj#hhjKubj5)}(h5``_h](j;)}(h4h]h4}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjubh)}(hjh](jN)}(hjh]h0https://perf.wiki.kernel.org/index.php/Main_Page}(hj hhhNhNubah}(h]h ]h"]h$]h&]name0https://perf.wiki.kernel.org/index.php/Main_Pagej^j uh1jMhj ubh)}(h2h]h}(h].https-perf-wiki-kernel-org-index-php-main-pageah ]h"]0https://perf.wiki.kernel.org/index.php/main_pageah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhM9hjubeh}(h]jjah ]h"]4ah$]h&]jeajjuh1j4hhhM9hj#hhjKubj5)}(hE``_h](j;)}(h5h]h5}(hj8 hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj4 ubh)}(hj6 h](jN)}(hj6 h]h@https://www.kernel.org/doc/html/latest/security/credentials.html}(hjI hhhNhNubah}(h]h ]h"]h$]h&]name@https://www.kernel.org/doc/html/latest/security/credentials.htmlj^jW uh1jMhjF ubh)}(hBh]h}(h]>https-www-kernel-org-doc-html-latest-security-credentials-htmlah ]h"]@https://www.kernel.org/doc/html/latest/security/credentials.htmlah$]h&]refurijW uh1hjlKhjF ubeh}(h]h ]h"]h$]h&]uh1hhhhM:hj4 ubeh}(h]j9ah ]h"]5ah$]h&](j4jejjuh1j4hhhM:hj#hhjKubj5)}(h=``_h](j;)}(h6h]h6}(hjv hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjr ubh)}(hjt h](jN)}(hjt h]h8http://man7.org/linux/man-pages/man7/capabilities.7.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name8http://man7.org/linux/man-pages/man7/capabilities.7.htmlj^j uh1jMhj ubh)}(h:h]h}(h]6http-man7-org-linux-man-pages-man7-capabilities-7-htmlah ]h"]8http://man7.org/linux/man-pages/man7/capabilities.7.htmlah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhM;hjr ubeh}(h]jtah ]h"]6ah$]h&](jojjtjjejejjuh1j4hhhM;hj#hhjKubj5)}(h7``_h](j;)}(h7h]h7}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h2http://man7.org/linux/man-pages/man2/ptrace.2.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name2http://man7.org/linux/man-pages/man2/ptrace.2.htmlj^j uh1jMhj ubh)}(h4h]h}(h]0http-man7-org-linux-man-pages-man2-ptrace-2-htmlah ]h"]2http://man7.org/linux/man-pages/man2/ptrace.2.htmlah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhM<hj ubeh}(h]j0ah ]h"]7ah$]h&]j+ajjuh1j4hhhM<hj#hhjKubj5)}(h?``_h](j;)}(h8h]h8}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h:https://en.wikipedia.org/wiki/Hardware_performance_counter}(hj hhhNhNubah}(h]h ]h"]h$]h&]name:https://en.wikipedia.org/wiki/Hardware_performance_counterj^j uh1jMhj ubh)}(h<h]h}(h]8https-en-wikipedia-org-wiki-hardware-performance-counterah ]h"]:https://en.wikipedia.org/wiki/hardware_performance_counterah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhM=hj ubeh}(h]jah ]h"]8ah$]h&]jajjuh1j4hhhM=hj#hhjKubj5)}(h:``_h](j;)}(h9h]h9}(hj0 hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj, ubh)}(hj. h](jN)}(hj. h]h5https://en.wikipedia.org/wiki/Model-specific_register}(hjA hhhNhNubah}(h]h ]h"]h$]h&]name5https://en.wikipedia.org/wiki/Model-specific_registerj^jO uh1jMhj> ubh)}(h7h]h}(h]3https-en-wikipedia-org-wiki-model-specific-registerah ]h"]5https://en.wikipedia.org/wiki/model-specific_registerah$]h&]refurijO uh1hjlKhj> ubeh}(h]h ]h"]h$]h&]uh1hhhhM>hj, ubeh}(h]jah ]h"]9ah$]h&]jajjuh1j4hhhM>hj#hhjKubj5)}(h4``_h](j;)}(h10h]h10}(hjn hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjj ubh)}(hjl h](jN)}(hjl h]h/http://man7.org/linux/man-pages/man5/acl.5.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name/http://man7.org/linux/man-pages/man5/acl.5.htmlj^j uh1jMhj| ubh)}(h1h]h}(h]-http-man7-org-linux-man-pages-man5-acl-5-htmlah ]h"]/http://man7.org/linux/man-pages/man5/acl.5.htmlah$]h&]refurij uh1hjlKhj| ubeh}(h]h ]h"]h$]h&]uh1hhhhM?hjj ubeh}(h]jah ]h"]10ah$]h&]jajjuh1j4hhhM?hj#hhjKubj5)}(h:``_h](j;)}(h11h]h11}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h5http://man7.org/linux/man-pages/man2/getrlimit.2.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name5http://man7.org/linux/man-pages/man2/getrlimit.2.htmlj^j uh1jMhj ubh)}(h7h]h}(h]3http-man7-org-linux-man-pages-man2-getrlimit-2-htmlah ]h"]5http://man7.org/linux/man-pages/man2/getrlimit.2.htmlah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhM@hj ubeh}(h]jah ]h"]11ah$]h&](jjejjuh1j4hhhM@hj#hhjKubj5)}(h<``_h](j;)}(h12h]h12}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h7http://man7.org/linux/man-pages/man5/limits.conf.5.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name7http://man7.org/linux/man-pages/man5/limits.conf.5.htmlj^j uh1jMhj ubh)}(h9h]h}(h]5http-man7-org-linux-man-pages-man5-limits-conf-5-htmlah ]h"]7http://man7.org/linux/man-pages/man5/limits.conf.5.htmlah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhMAhj ubeh}(h]jah ]h"]12ah$]h&]jajjuh1j4hhhMAhj#hhjKubj5)}(h/``_h](j;)}(h13h]h13}(hj( hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj$ ubh)}(hj& h](jN)}(hj& h]h*https://sites.google.com/site/fullycapable}(hj9 hhhNhNubah}(h]h ]h"]h$]h&]name*https://sites.google.com/site/fullycapablej^jG uh1jMhj6 ubh)}(h,h]h}(h](https-sites-google-com-site-fullycapableah ]h"]*https://sites.google.com/site/fullycapableah$]h&]refurijG uh1hjlKhj6 ubeh}(h]h ]h"]h$]h&]uh1hhhhMBhj$ ubeh}(h]jah ]h"]13ah$]h&]jajjuh1j4hhhMBhj#hhjKubj5)}(h7``_h](j;)}(h14h]h14}(hjf hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hjb ubh)}(hjd h](jN)}(hjd h]h2http://man7.org/linux/man-pages/man8/auditd.8.html}(hjw hhhNhNubah}(h]h ]h"]h$]h&]name2http://man7.org/linux/man-pages/man8/auditd.8.htmlj^j uh1jMhjt ubh)}(h4h]h}(h]0http-man7-org-linux-man-pages-man8-auditd-8-htmlah ]h"]2http://man7.org/linux/man-pages/man8/auditd.8.htmlah$]h&]refurij uh1hjlKhjt ubeh}(h]h ]h"]h$]h&]uh1hhhhMChjb ubeh}(h]jah ]h"]14ah$]h&]j ajjuh1j4hhhMChj#hhjKubj5)}(h6``_h](j;)}(h15h]h15}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h1https://man7.org/linux/man-pages/man8/sudo.8.html}(hj hhhNhNubah}(h]h ]h"]h$]h&]name1https://man7.org/linux/man-pages/man8/sudo.8.htmlj^j uh1jMhj ubh)}(h3h]h}(h]/https-man7-org-linux-man-pages-man8-sudo-8-htmlah ]h"]1https://man7.org/linux/man-pages/man8/sudo.8.htmlah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhMDhj ubeh}(h]jah ]h"]15ah$]h&]jajjuh1j4hhhMDhj#hhjKubj5)}(h;``_h](j;)}(h16h]h16}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j:hj ubh)}(hj h](jN)}(hj h]h6https://git.kernel.org/pub/scm/libs/libcap/libcap.git/}(hj hhhNhNubah}(h]h ]h"]h$]h&]name6https://git.kernel.org/pub/scm/libs/libcap/libcap.git/j^j uh1jMhj ubh)}(h8h]h}(h]3https-git-kernel-org-pub-scm-libs-libcap-libcap-gitah ]h"]6https://git.kernel.org/pub/scm/libs/libcap/libcap.git/ah$]h&]refurij uh1hjlKhj ubeh}(h]h ]h"]h$]h&]uh1hhhhMEhj ubeh}(h]j8ah ]h"]16ah$]h&](j3jejjuh1j4hhhMEhj#hhjKubeh}(h] bibliographyah ]h"] bibliographyah$]h&]uh1hhhhhhhhM4ubeh}(h](perf-events-and-tool-securityheh ]h"](perf events and tool security perf_securityeh$]h&]uh1hhhhhhhhKexpect_referenced_by_name}j* hsexpect_referenced_by_id}hhsubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksentryfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjT error_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourcehÌ _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}(1]ha2](j j5jojjjije3](j!jHe4]j[a8]ja9]ja5](j*je6](jejjjjj[je13]ja14]ja7]j!a10]j}a15]ja16](j)je11](j|je12]jaurefids}h]hasnameids}(j* hj) j& jIjFjNjKjyjvj<j9j jjjjjj! j jwjjhjejjjjjj0jjj1 jjj# j jo j9ja j^ j jtj j j j0j j j) jj j jg jjY jV j jj j j jj j j! jj j j_ jjQ jN j jj j j jj j j j8j j u nametypes}(j* j) jIjNjyj<j jjj! jwjhjjjjj1 j# jo ja j j j j j) j jg jY j j j j j! j j_ jQ j j j j j j uh}(hhj& hjFhjhjj j+j!j?j5jRjHjej[jyjojjjjj4j*jKjLjojejjjjjjj jj+j!jvjQjtjjjj}jjjjj3j)jjjej[j9j|jjj(jjjjj?jjPjsjijj|jjjjjjjjj j#jj6jej_jjzjjj0jjjjjjj j j9j4 j^ jX jtjr j j j0j j j jj j j jj, jV jP jjj j j jj j j jj j j jj$ jN jH jjb j j jj j j j8j j j u footnote_refs}(j ]haj ](j j5jojjjijej ](j!jHej ]j[aj ]jaj ]jaj ](j*jej ](jejjjjj[jej ]jaj ]jaj ]j!aj ]j}aj ]jaj ](j)jej ](j|jej ]jau citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes](j6jzjjj4 jr j j j, jj j j j$ jb j j e citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}jb K/sRparse_messages](hsystem_message)}(hhh]h)}(h:Enumerated list start value not ordinal-1: "2" (ordinal 2)h]h>Enumerated list start value not ordinal-1: “2” (ordinal 2)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj ubah}(h]h ]h"]h$]h&]levelKtypeINFOsourcehÌlineKuh1j hjQhhhhhKubj )}(hhh]h)}(h:Enumerated list start value not ordinal-1: "2" (ordinal 2)h]h>Enumerated list start value not ordinal-1: “2” (ordinal 2)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj ubah}(h]h ]h"]h$]h&]levelKtypej sourcehÌlineKuh1j hjQhhhhhKubj )}(hhh]h)}(h:Enumerated list start value not ordinal-1: "3" (ordinal 3)h]h>Enumerated list start value not ordinal-1: “3” (ordinal 3)}(hj# hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj ubah}(h]h ]h"]h$]h&]levelKtypej sourcehÌlineKuh1j hjQhhhhhKubetransform_messages]j )}(hhh]h)}(hhh]h3Hyperlink target "perf-security" is not referenced.}hj@ sbah}(h]h ]h"]h$]h&]uh1hhj= ubah}(h]h ]h"]h$]h&]levelKtypej sourcehÌlineKuh1j uba transformerN include_log] decorationNhhub.