This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
RE: [PATCH] clone3: validate stack arguments
- From: David Laight <David dot Laight at ACULAB dot COM>
- To: 'Christian Brauner' <christian dot brauner at ubuntu dot com>, "linux-kernel at vger dot kernel dot org" <linux-kernel at vger dot kernel dot org>, Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Cc: Arnd Bergmann <arnd at arndb dot de>, Kees Cook <keescook at chromium dot org>, "Jann Horn" <jannh at google dot com>, David Howells <dhowells at redhat dot com>, Ingo Molnar <mingo at redhat dot com>, Oleg Nesterov <oleg at redhat dot com>, Linus Torvalds <torvalds at linux-foundation dot org>, Peter Zijlstra <peterz at infradead dot org>, "linux-api at vger dot kernel dot org" <linux-api at vger dot kernel dot org>, "stable at vger dot kernel dot org" <stable at vger dot kernel dot org>
- Date: Thu, 31 Oct 2019 11:41:06 +0000
- Subject: RE: [PATCH] clone3: validate stack arguments
- References: <20191031113608.20713-1-christian.brauner@ubuntu.com>
From: Christian Brauner
> Sent: 31 October 2019 11:36
...
> /* Intentional user visible API change */
> clone3() was released with 5.3. Currently, it is not documented and very
> unclear to userspace how the stack and stack_size argument have to be
> passed. After talking to glibc folks we concluded that trying to change
> clone3() to setup the stack instead of requiring userspace to do this is
> the right course of action.
What happens if someone 'accidentally' runs a program compiled for
the new API on a system running the existing 5.3 kernel?
While it won't work, it needs to die reasonably gracefully.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)