1. 08 Jul, 2009 3 commits
    • Catalin Marinas's avatar
      kmemleak: Scan objects allocated during a scanning episode · 2587362e
      Catalin Marinas authored
      Many of the false positives in kmemleak happen on busy systems where
      objects are allocated during a kmemleak scanning episode. These objects
      aren't scanned by default until the next memory scan. When such object
      is added, for example, at the head of a list, it is possible that all
      the other objects in the list become unreferenced until the next scan.
      
      This patch adds checking for newly allocated objects at the end of the
      scan and repeats the scanning on these objects. If Linux allocates
      new objects at a higher rate than their scanning, it stops after a
      predefined number of passes.
      Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      2587362e
    • Catalin Marinas's avatar
      kmemleak: Do not acquire scan_mutex in kmemleak_open() · b87324d0
      Catalin Marinas authored
      Initially, the scan_mutex was acquired in kmemleak_open() and released
      in kmemleak_release() (corresponding to /sys/kernel/debug/kmemleak
      operations). This was causing some lockdep reports when the file was
      closed from a different task than the one opening it. This patch moves
      the scan_mutex acquiring in kmemleak_write() or kmemleak_seq_start()
      with releasing in kmemleak_seq_stop().
      Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      b87324d0
    • Catalin Marinas's avatar
      kmemleak: Remove the reported leaks number limitation · 288c857d
      Catalin Marinas authored
      Since the leaks are no longer printed to the syslog, there is no point
      in keeping this limitation. All the suspected leaks are shown on
      /sys/kernel/debug/kmemleak file.
      Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      288c857d
  2. 07 Jul, 2009 3 commits
  3. 06 Jul, 2009 34 commits