summaryrefslogtreecommitdiffstats
path: root/security/yama
diff options
context:
space:
mode:
authorMateusz Guzik <mjguzik@gmail.com>2024-06-20 19:15:27 +0200
committerJohn Johansen <john.johansen@canonical.com>2024-07-24 20:05:14 +0200
commitf4fee216df7d28b87d1c9cc60bcebfecb51c1a05 (patch)
tree43f46dacda613f67cda982c55588f0dd3e457de6 /security/yama
parentapparmor: test: add MODULE_DESCRIPTION() (diff)
downloadlinux-f4fee216df7d28b87d1c9cc60bcebfecb51c1a05.tar.xz
linux-f4fee216df7d28b87d1c9cc60bcebfecb51c1a05.zip
apparmor: try to avoid refing the label in apparmor_file_open
If the label is not stale (which is the common case), the fact that the passed file object holds a reference can be leverged to avoid the ref/unref cycle. Doing so reduces performance impact of apparmor on parallel open() invocations. When benchmarking on a 24-core vm using will-it-scale's open1_process ("Separate file open"), the results are (ops/s): before: 6092196 after: 8309726 (+36%) Signed-off-by: Mateusz Guzik <mjguzik@gmail.com> Signed-off-by: John Johansen <john.johansen@canonical.com>
Diffstat (limited to 'security/yama')
0 files changed, 0 insertions, 0 deletions