apparmor/libraries/libapparmor/testsuite/test_multi/status-filesystem-enabled.out

START
File: status-filesystem-enabled.in
Event type: AA_RECORD_INVALID
Avoid aa-notify crash on log events without operation= Some STATUS log events trigger a crash in aa-notify because the log line doesn't have operation=. Examples are: type=AVC msg=audit(1630913351.586:4): apparmor="STATUS" info="AppArmor Filesystem Enabled" pid=1 comm="swapper/0" type=AVC msg=audit(1630913352.610:6): apparmor="STATUS" info="AppArmor sha1 policy hashing enabled" pid=1 comm="swapper/0" Fix this by not looking at log events without operation= Also add one of the example events as libapparmor testcase. Fixes: https://gitlab.com/apparmor/apparmor/-/issues/194 2021-09-06 16:54:33 +02:00			`START`
			`File: status-filesystem-enabled.in`
			`Event type: AA_RECORD_INVALID`