touch-packages team mailing list archive

[Steve Beattie <sbeattie@xxxxxxxxxx>]

Commits to address these have been applied to the 2.8 and trunk apparmor
branches.

The ubuntu packages should also get a fix for this.

** Changed in: apparmor
       Status: In Progress => Fix Committed

** Changed in: apparmor/2.8
       Status: In Progress => Fix Committed

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: apparmor (Ubuntu)
       Status: New => Triaged

-- 
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/1340927

Title:
  aa-notify memory leak

Status in AppArmor Linux application security framework:
  Fix Committed
Status in AppArmor 2.8 series:
  Fix Committed
Status in “apparmor” package in Ubuntu:
  Triaged

Bug description:
  My kern.log is filled by lots of messages so aa-notify tries to parse
  them on first run.

  My OS is going down when there's no memory left because aa-notify
  leaks.

  I've found that leak is in /usr/bin/aa-notify file in function
  parse_message.

  If I comment lines from 
  my ($test) = LibAppArmorc::parse_record($msg);
  to
  LibAppArmorc::free_record($test);
  then all goes fine. Program parses file and no memory leak is happened.

  Do I've got sources of my version (libapparmor-perl (2.8.0-5.1) from ubuntu) and found that some variables from aa_log_record struct were not freed by the free_record function. These are
  char *net_local_addr;
  char *net_foreign_addr;

  Could this be a reason of a leak?

  I haven't much time right now to compile and run tests. So I posted
  just information I've found and commented lines in bugged function to
  get my system working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1340927/+subscriptions