mir/apparmor
2
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor synced 2025-09-03 15:55:46 +00:00
Code Issues Releases Wiki Activity

Update apparmor_kernel_development_guide_notifications

John Johansen
2018-12-06 00:39:43 +00:00
parent 17d282c522
commit 7402c6306a
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
apparmor_kernel_development_guide_notifications.md

@@ -83,7 +83,20 @@ And at hook exit
If a notification is determined to be needed the audit message is queued up on the aa_notify struct. And it is handled in do_notify at the end of the hook. This allows us to avoid apparmor internal locking and also to group multiple notifications into a single message. If a notification is determined to be needed the audit message is queued up on the aa_notify struct. And it is handled in do_notify at the end of the hook. This allows us to avoid apparmor internal locking and also to group multiple notifications into a single message.
## ?? ## Waiting
- we use a wait_queue instead of a completion queue
- as there maybe multiple tasks listening, that may wake up on the same event.
- because events are at the policy ns level, we have a single wait_queue per ns.
- waiter
- each listener whos filter matches a notification will be woken/receive wakeup?
??? Instead of having a message on multiple queues there is a single queue of notifications per ns
- notifications removed when every listener has processed it OR timeout OR rate limiting drops it