linux-kernel - [RFC][PATCH 0/2] kmemleak: Fix some false positives with special scan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1273821401-26578-1-git-send-email-Hiroshi.DOYU@nokia.com>
Date:	Fri, 14 May 2010 10:16:39 +0300
From:	Hiroshi DOYU <Hiroshi.DOYU@...ia.com>
To:	linux-kernel@...r.kernel.org
Cc:	catalin.marinas@....com, Hiroshi DOYU <Hiroshi.DOYU@...ia.com>
Subject: [RFC][PATCH 0/2] kmemleak: Fix some false positives with special scan

Hi,

I always get the false positives for the iommu 1st level page table
since it stores the pointer to the 2nd level page table, but it is
converted to a physical address with some attribute
bits. "kmemleak_ignore" can cover this problem, but will loose the
advantage of powerful kmemleak detection. So I experimentally
implement the APIs to register the special scan area with the address
conversion function. I'm not sure if this APIs make sense or not, but
it works for our OMAP IOMMU case now.

Any comment would be appreciated.

Hiroshi DOYU (2):
  kmemleak: Fix some false positives with special scan
  kmemleak: test: Add a special scan test case

 include/linux/kmemleak.h   |    4 ++
 mm/Makefile                |    2 +-
 mm/kmemleak-special-test.c |   89 ++++++++++++++++++++++++++++++++++++++++++++
 mm/kmemleak.c              |   83 +++++++++++++++++++++++++++++++++++++++-
 4 files changed, 174 insertions(+), 4 deletions(-)
 create mode 100644 mm/kmemleak-special-test.c

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/