Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693470 - libauparse memory leak
Summary: libauparse memory leak
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: audit
Version: ---
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: 8.0
Assignee: Steve Grubb
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 22:48 UTC by Steve Grubb
Modified: 2019-04-03 10:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Steve Grubb 2019-03-27 22:48:54 UTC
Description of problem:
It was reported upstream that libauparse was leaking memory.
https://www.redhat.com/archives/linux-audit/2019-March/msg00103.html

The leak is pretty big. Normally libauparse is used for analytic tools that need to parse audit events. Of these, all are known to be quick run to completion and exit with one exception. The sedispatch program does some basic analysis of the audit trail and can quickly grow depending on how many avcs it gets.


Version-Release number of selected component (if applicable):
audit-3.0-0.10.20180831git0047a6c.el8.x86_64


Note You need to log in before you can comment on or make changes to this bug.