linux-kernel - Re: [PATCH] sched: make task_nice available to non-GPL modules

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

Date:	Thu, 6 Mar 2008 11:41:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pavel Roskin <proski@....org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: make task_nice available to non-GPL modules

* Pavel Roskin <proski@....org> wrote:

> The API is trivial, and so is the implementation.  Linux priorities 
> are exposed to the userspace, so nobody should claim that software 
> aware of Linux priorities is a derived work of the kernel.
> 
> The complementary function set_user_nice() is available to non-GPL 
> modules.  If the module can set the priority, it should be able to 
> read it back.

i've applied this, but i removed the (incorrect) legal interpretation in
the commit message. We simply make it available generally, and the
export is not restricted to clearly internal modules only. (but that
does not mean that a module using it is not a derived work)

this is a fine but important distinction. If a module uses a GPL symbol, 
it is a strong hint of being derived work. But by not using GPL-only 
symbols (but using other symbols - or not using kernel symbols at all) 
it might still be derived work and even if it's not derived work, it 
might still fall under the GPL.

in other words: EXPORT_SYMBOL does not mean and never meant 
EXPORT_SYMBOL_NON_GPL.

EXPORT_SYMBOL_GPL is EXPORT_SYMBOL_I_ADMIT_MY_MODULE_IS_DERIVED, and 
EXPORT_SYMBOL is EXPORT_SYMBOL_ASK_YOUR_LAWYER.

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