Merge parser: misc fixes on apparmor.d man page

Signed-off-by: Georgia Garcia <georgia.garcia@canonical.com>

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1516
Approved-by: John Johansen <john@jjmx.net>
Merged-by: John Johansen <john@jjmx.net>
This commit is contained in:
John Johansen 2025-01-31 21:54:08 +00:00
commit 4765bcd7bc

View file

@ -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 for mounts matching the exactly specified options. For example, an AppArmor
policy with the following rule: policy with the following rule:
mount options=ro /dev/foo -E<gt> /mnt/, mount options=ro /dev/foo -> /mnt/,
Would match: 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 writing mount rules which might help to logically break up a conditional. For
example, if an AppArmor policy has the following rule: 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: both of these mount commands will match:
@ -1319,7 +1319,7 @@ Example IO_URING rules:
=over 4 =over 4
# Allow io_uring operations # Allow io_uring operations
io_ring, io_uring,
# Allow creation of a polling thread # Allow creation of a polling thread
io_uring sqpoll, io_uring sqpoll,