linux-kernel - Re: [PATCH] powerpc/eeh: remove eeh_event

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]

Message-ID: <20110818073452.GE13572@htj.dyndns.org>
Date:	Thu, 18 Aug 2011 09:34:52 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>,
	Linas Vepstas <linasvepstas@...il.com>,
	Matt Fleming <matt@...sole-pimps.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/eeh: remove eeh_event_handler()->daemonize()

Hello,

On Wed, Aug 17, 2011 at 07:27:13PM +0200, Oleg Nesterov wrote:
> Btw. Perhaps we should kill CLONE_KERNEL? And note that the only
> user is eeh_thread_launcher().
> 
> The problem is, CLONE_KERNEL looks as "use me if you want to create
> a kernel thread". But CLONE_SIGHAND means the kernel thread should
> not play with signals, and this is not obvious.

I guess it predates kthread().  There's no reason to use
kernel_thread() directly outside of a few core places, so removing it
sounds like a pretty good idea.

Thanks.

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