linux-kernel - Re: [RFC][v6][PATCH 0/9] clone_with

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: <1252668148.7126.13.camel@laptop>
Date:	Fri, 11 Sep 2009 13:22:28 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, Oren Laadan <orenl@...columbia.edu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Pavel Emelyanov <xemul@...nvz.org>,
	Andrew Morton <akpm@...l.org>, torvalds@...ux-foundation.org,
	mikew@...gle.com, mingo@...e.hu, hpa@...or.com,
	Nathan Lynch <nathanl@...tin.ibm.com>, arnd@...db.de,
	container@...ibm.com, sukadev@...ibm.com
Subject: Re: [RFC][v6][PATCH 0/9] clone_with_pids() syscall

On Wed, 2009-09-09 at 23:06 -0700, Sukadev Bhattiprolu wrote:

> Based on these requirements and constraints, we have been exploring a couple
> of system call interfaces and appreciate any iput.  

Why not have something like:

struct clone_struct {
	u32 size;
	u32 __reserved;
	u64 flags;
	u64 child_stack;
	u32 child_tid;
	u32 parent_tid;
};

struct clone_pid_struct {
	u32 nr;
	pid_t pids[];
};

int clone2(struct clone_struct *cs, struct clone_pid_struct *cps);

If you then get passed a longer clone_struct than you know about, all is
well IFF the tail is 0, otherwise fail with -E2BIG.

If you get passed a short clone_struct, zero out the tail.

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