search for: avc_node

...7 68K idr_layer_cache 118 41 34% 0.06K 2 59 8K blkdev_ioc 112 32 28% 0.03K 1 112 4K tcp_bind_bucket 110 56 50% 0.17K 5 22 20K file_lock_cache 106 35 33% 0.07K 2 53 8K avc_node 105 98 93% 1.50K 21 5 168K TCP 105 100 95% 1.04K 15 7 120K bio_map_info 92 1 1% 0.04K 1 92 4K dnotify_cache 80 18 22% 0.19K 4 20 16K tw_sock_TCP 70 44 62% 0.27K 5...

...17 7 68K idr_layer_cache 118 41 34% 0.06K 2 59 8K blkdev_ioc 112 32 28% 0.03K 1 112 4K tcp_bind_bucket 110 56 50% 0.17K 5 22 20K file_lock_cache 106 35 33% 0.07K 2 53 8K avc_node 105 98 93% 1.50K 21 5 168K TCP 105 100 95% 1.04K 15 7 120K bio_map_info 92 1 1% 0.04K 1 92 4K dnotify_cache 80 18 22% 0.19K 4 20 16K tw_sock_TCP 70 44 62% 0.27K 5...

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm: