From 998ee0595e28f8ad5923607fdfae2a2d4397804b Mon Sep 17 00:00:00 2001 From: Georgia Garcia Date: Fri, 31 Jan 2025 18:23:14 -0300 Subject: [PATCH] parser: misc fixes on apparmor.d man page Signed-off-by: Georgia Garcia --- parser/apparmor.d.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/parser/apparmor.d.pod b/parser/apparmor.d.pod index a174bbc37..9a9dc6714 100644 --- a/parser/apparmor.d.pod +++ b/parser/apparmor.d.pod @@ -1024,7 +1024,7 @@ If a conditional is specified using '=', then the rule only grants permission for mounts matching the exactly specified options. For example, an AppArmor policy with the following rule: - mount options=ro /dev/foo -E /mnt/, + mount options=ro /dev/foo -> /mnt/, Would match: @@ -1071,7 +1071,7 @@ grants permission for each set of options. This provides a shorthand when writing mount rules which might help to logically break up a conditional. For example, if an AppArmor policy has the following rule: - mount options=ro options=atime + mount options=ro options=atime, both of these mount commands will match: @@ -1319,7 +1319,7 @@ Example IO_URING rules: =over 4 # Allow io_uring operations - io_ring, + io_uring, # Allow creation of a polling thread io_uring sqpoll,