** Changed in: apparmor
Status: New => Fix Released
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: apparmor (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2083435
Title:
AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Oracular:
Fix Released
Bug description:
Commit 3c825eb001d33bb6f2480c4f78df03aee4c40396 in the Gitlab upstream
adds a field called `execpath` to the `aa_log_record` struct. This
field was added in the middle of the struct instead of the end,
causing an ABI break in libapparmor without a corresponding major
version number bump. This commit landed between v4.0.3 and
v4.1.0-beta1, and unfortunately, Oracular currently packages
v4.1.0-beta1.
Thus, we need to land a bugfix patch to move the `execpath` field to
the end of the struct ASAP to prevent an ABI break from making it into
the Oracular release. The patch is attached below and is available as
commit c86c87e8868c72e5ab2084b5bf783cd5ca800a9b in the Gitlab repo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
