linux-kernel - Re: [RFC, PATCH 1/3] introduce SYS_CLONE

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: <20070529055647.221251F8511@magilla.localdomain>
Date:	Mon, 28 May 2007 22:56:47 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	ebiederm@...ssion.com (Eric W. Biederman)
Cc:	"Albert Cahalan" <acahalan@...il.com>,
	linux-kernel@...r.kernel.org, jengelh@...ux01.gwdg.de,
	holt@....com, oleg@...sign.ru
Subject: Re: [RFC, PATCH 1/3] introduce SYS_CLONE_MASK

> Having the kernel not reparent user processes to init is an interesting
> idea, especially when those processes have not existed.  I'm not
> certain that is POSIX complaint and otherwise backwards compatible.

It's hard to see how it would work.  There has to be some parent PID.  The
reason using 1 makes sense is that it is always there.  Anything >0 and not
the PID of some live process could be reused for a new process at some point.


Thanks,
Roland
-
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/