linux-kernel - Re: init's children list is long and slows reaping children.

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

Message-ID: <20070406173123.GA1875@elte.hu>
Date:	Fri, 6 Apr 2007 19:31:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Oleg Nesterov <oleg@...sign.ru>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Robin Holt <holt@....com>, Chris Snook <csnook@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: init's children list is long and slows reaping children.


* Ingo Molnar <mingo@...e.hu> wrote:

> putting the freshly reaped tasks at the 'head' of the list is just a 
> fancy (and incomplete) way of splitting the list up into two lists, and 
> i'd advocate a clean split. Just like have have split the ptrace_list 
                                          ^---s/have/we
> away from the main list too.

and in this sense your suggestion will happen:

> > I'd almost prefer to just not add kernel threads to any parent 
> > process list *at*all*.

because that way kernel threads will never show up in the to-be-reaped 
list, they'll only show up in the main list that represents the tree of 
tasks.

	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/