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: <1252669205.7126.23.camel@laptop>
Date:	Fri, 11 Sep 2009 13:40:05 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	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>, container@...ibm.com,
	sukadev@...ibm.com
Subject: Re: [RFC][v6][PATCH 0/9] clone_with_pids() syscall

On Fri, 2009-09-11 at 13:34 +0200, Arnd Bergmann wrote:
> On Friday 11 September 2009, Peter Zijlstra wrote:

> > 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.
> 
> I would leave out the size argument. We can put a few reserved fields
> and flag bits in there for possible extensions, but if we ever run out
> of these, just define a new syscall.

Why? If we can avoid this new syscall isn't that nicer?

> Also, if you're passing a struct, why not put nr_pids in there, and
> replace clone_pid_struct with a simple array? That would give us

Sure..


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