linux-kernel - Re: [PATCH] tracing: Export key trace event symbols

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]

Message-ID: <20150421093820.6a565f58@gandalf.local.home>
Date:	Tue, 21 Apr 2015 09:38:20 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ron Rechenmacher <ron@...l.gov>
Cc:	Christoph Hellwig <hch@...radead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing: Export key trace event symbols

On Tue, 21 Apr 2015 07:19:30 -0500
Ron Rechenmacher <ron@...l.gov> wrote:

> I see in the reference I mentioned below (https://patches.linaro.org/28821/),
> and in the current mm source, that some tracepoint symbols are already EXPORTed,
> but not _GPL. I do not know the fine points between "GPL-ed" and "non-GPL-ed" symbol
> exporting.  Would it make a difference if my patch proposed non-GPL exporting?

The only reason there's non GPL exports for tracepoints is because
tracepoints were used in header files, and called by static inlines
like kfree() and such that were already exported non-gpl.

I believe we removed all tracepoints from static inlines and headers
because they were causing other problems (you don't want tracepoint
code inlined all over the place, it bloats the kernel).

I may look into cleaning up the kernel and removing the
EXPORT_TRACEPOINT_SYMBOL().

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