linux-kernel - Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of each asynchronous levels

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]

Date:	Tue, 7 Jul 2015 16:07:58 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Christoph Lameter <cl@...ux.com>,
	Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 2/3] kmod: Add up-to-date explanations on the purpose of
 each asynchronous levels

On Mon,  6 Jul 2015 17:33:40 +0200 Frederic Weisbecker <fweisbec@...il.com> wrote:

> There seem to be quite some confusions on the comments, likely due to
> changes that came after them.
> 
> Now since it's very non obvious why we have 3 levels of asynchronous
> code to implement usermodehelpers, it's important to comment in detail
> the reason of this layout.

There are still a few references to keventd in there.  One of them is
simply wrong: "runs as a child of keventd".  The userspace code is
actually a child of the khelper thread, yes?

I guess we should remove all kernel references to "keventd".  It got
renamed to "kworker".
--
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/