linux-kernel - kernel_thread() usage found in staging

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

Message-ID: <804dabb00903130126m79272087xd2fd452e2712abac@mail.gmail.com>
Date:	Fri, 13 Mar 2009 16:26:27 +0800
From:	Peter Teoh <htmldeveloper@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Greg KH <greg@...ah.com>
Subject: kernel_thread() usage found in staging

>From Documentation/feature_removal_schedule.txt, it is well-known that
kernel_thread() API usage is discouraged, but in staging we still
routinely see its use.   Perhaps the original driver owner have
overlooked this?

Thanks.

./rt2870/common/2870_rtmp_init.c:
	pid_number = kernel_thread(MlmeThread, pAd, CLONE_VM);
	pid_number = kernel_thread(RTUSBCmdThread, pAd, CLONE_VM);
	pid_number = kernel_thread(TimerQThread, pAd, CLONE_VM);

./usbip/usbip_common.c:
	retval = kernel_thread(usbip_thread, (void *)&ud->tcp_rx, 0);
	retval = kernel_thread(usbip_thread, (void *)&ud->tcp_tx, 0);

./usbip/usbip_event.c:
	kernel_thread(usbip_thread, (void *)eh, 0);

./epl/ShbIpc-LinuxKernel.c:
	    kernel_thread(ShbIpcThreadSignalNewData, pShbInstance_p,
	    kernel_thread(ShbIpcThreadSignalJobReady, pShbInstance_p,

./epl/EplSdoUdpu.c:
	    kernel_thread(EplSdoUdpThread, &SdoUdpInstance_g, CLONE_KERNEL);


-- 
Regards,
Peter Teoh
--
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/