linux-kernel - Re: kernel_thread() for non-GPL drivers

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:	Tue, 2 Jun 2015 21:31:38 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Ani Sinha <ani@...sta.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	fruggeri <fruggeri@...sta.com>,
	Ivan Delalande <colona@...sta.com>
Subject: Re: kernel_thread() for non-GPL drivers

On Tue, Jun 02, 2015 at 12:43:15PM -0700, Ani Sinha wrote:

> So my question to you is, which api (for x86) are drivers supposed to
> use if kernel_thread() is no longer available? It looks to me like
> maybe we can use kthread_run() which eventually lazily creates a
> kernel thread. Is my understanding correct?

First of all, what the hell does it have to do with GPL?  Or modules
vs. built-in, for that matter...  kernel_thread() is _not_ what it
used to be way back and export or no export, your driver isn't going
to be happy with it.

kthread_run() had been there for more than 11 years, for crying out loud!
--
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/