apparmor.common.AppArmorBug: exec permissions requested for foobar, but mode is {'x'} instead of exec. This should not happen - please open a bugreport!
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
New
|
Undecided
|
Unassigned |
Bug Description
∞ aa-logprof -m 1566678483.715:202
Reading log entries from /var/log/
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
File "/usr/lib/
apparmor.
File "/usr/lib64/
handle_
File "/usr/lib64/
raise AppArmorBug('exec permissions requested for %(exec_target)s, but mode is %(mode)s instead of exec. This should not happen - please open a bugreport!' % {'exec_target': exec_target, 'mode':mode})
apparmor.
An unexpected error occoured!
Do you still have the audit.log that triggers this? If yes, can you please attach it? (If you don't want to attach the full log, the relevant lines for "...//proc- macro2- 0d62d90a89317e1 3/build- script- build" might be enough, but in this case please test if they are enough to reproduce this bug using "aa-logprof -f the_shortened_ audit.log" )
Looking at the code, I'm quite sure that typ == 'path' because that's the only way how you could reach this code section, but I'm surprised that you get an exec event for 'path'.
As a sidenote: This part of the code was completely rewritten in latest master, so this bug likely "only" affects the 2.11, 2.12 and 2.13 branches - or at least affects master in a different way ;-)