linux-kernel - Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session

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:	Mon, 26 Nov 2007 12:23:26 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Oleg Nesterov <oleg@...sign.ru>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Pavel Emelyanov <xemul@...nvz.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session

ebiederm@...ssion.com (Eric W. Biederman) writes:


> Hmm.  I wonder if we could ensure kernel_thread always
> returns a global pid_t, and then reallocate the struct
> pid for the task we have just daemonized so that it only
> has a single pid in the init_pid_ns.

Well we can't reallocate the struct pid, if anyone was using
it we would have problems, but we can certainly remove all
pid_t values except for those in the init_pid_ns.

We definitely have some serious issues with kernel_thread
and signal sending though.

Eric

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