-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i/prompting: do not error when converting empty abstract perms to AA perms #14975
i/prompting: do not error when converting empty abstract perms to AA perms #14975
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #14975 +/- ##
=========================================
Coverage ? 78.03%
=========================================
Files ? 1143
Lines ? 152647
Branches ? 0
=========================================
Hits ? 119121
Misses ? 26188
Partials ? 7338
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Sat Jan 25 02:48:45 UTC 2025 Failures:Preparing:
Executing:
Restoring:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
…perms It's reasonable that one might wish to convert an empty list of abstract permissions to AppArmor permissions, such as when one is constructing an allowed permissions set where all permissions are denied. It was incorrect to treat this as an error, and furthermore, the only current caller of `AbstractPermissionsToAppArmorPermissions` which actually uses the error value is in `requestprompts`, which logs a logger notice on an error. So we were getting false-positive errors in the journalctl log. This commit fixes that issue. Signed-off-by: Oliver Calder <[email protected]>
0da5340
to
edb36c2
Compare
It's reasonable that one might wish to convert an empty list of abstract permissions to AppArmor permissions, such as when one is constructing an allowed permissions set where all permissions are denied.
It was incorrect to treat this as an error, and furthermore, the only current caller of
AbstractPermissionsToAppArmorPermissions
which actually uses the error value is inrequestprompts
, which logs a logger notice on an error. So we were getting false-positive errors in the journalctl log. This commit fixes that issue.This addresses https://warthogs.atlassian.net/browse/SNAPDENG-31322