Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-coresight-backports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-coresight-backports
  • Repository
Switch branch/tag
  • linux-coresight-backports
  • security
  • apparmor
  • policy.c
Find file BlameHistoryPermalink
  • John Johansen's avatar
    apparmor: fix memory leak when deduping profile load · 3ddae987
    John Johansen authored Apr 13, 2018
    AppArmor is leaking the newly loaded profile and its proxy when
    the profile is an exact match to the currently loaded version.
    
    In this case the dedup check results in the profile being skipped and
    put without dealing with the proxy ref thus not breaking a circular
    refcount and causing a leak.
    
    BugLink: http://bugs.launchpad.net/bugs/1750594
    Fixes: 5d5182ca
    
     ("apparmor: move to per loaddata files, instead of replicating in profiles")
    Signed-off-by: default avatarJohn Johansen <john.johansen@canonical.com>
    3ddae987