linux-kernel - Re: [PATCH] Documentation: extend use case for EXPORT_SYMBOL

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150528130923.42f34540@lwn.net>
Date:	Thu, 28 May 2015 13:09:23 -0600
From:	Jonathan Corbet <corbet@....net>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	mingo@...e.hu, gnomes@...rguk.ukuu.org.uk,
	gregkh@...uxfoundation.org, jkosina@...e.cz, bhelgaas@...gle.com,
	linux-pci@...r.kernel.org, xen-devel@...ts.xenproject.org,
	bp@...e.de, "Luis R. Rodriguez" <mcgrof@...e.com>
Subject: Re: [PATCH] Documentation: extend use case for EXPORT_SYMBOL_GPL()

On Thu, 28 May 2015 11:56:01 -0700
"Luis R. Rodriguez" <mcgrof@...not-panic.com> wrote:

> +    Some maintainers and developers may however have a preference to
> +    require EXPORT_SYMBOL_GPL() when adding any new APIs or functionality.

As a nit, I would take out "have a preference to".

>From what I can tell, there are developers who think this position makes
little sense and, perhaps, risks diluting the value of EXPORT_SYMBOL_GPL()
by attaching it to everything.  My inclination, though, would be to accept
this change as documentation of clear existing practice; whether that
practice should change is, I think, a separate discussion.

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