linux-kernel - Re: Exporting kmemleak.h to userspace

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 03 Sep 2009 14:18:59 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: Exporting kmemleak.h to userspace

On Thu, 2009-09-03 at 09:23 +0300, Pekka Enberg wrote:
> On Thu, Sep 3, 2009 at 3:29 AM, Luis R. Rodriguez<mcgrof@...il.com> wrote:
> > I was reviewing kmemleak code and noticed kmemleak.h went exported to
> > userspace under include/linux/kmemleak.h. Do we expect userspace to
> > use this stuff somehow? All relevant kmemleak structs are kept
> > private, I'm curious what userspace apps would use this.
> 
> AFAICT, nobody. Catalin, why is the header exported?

I haven't done anything specifically to export it. It probably gets
included via other files. Is adding #ifdef __KERNEL__ enough to avoid
this problem?

-- 
Catalin

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