From: David Laight <David.Laight@ACULAB.COM>
To: 'Christian Brauner' <christian.brauner@ubuntu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>,
"Jann Horn" <jannh@google.com>,
David Howells <dhowells@redhat.com>,
Ingo Molnar <mingo@redhat.com>, Oleg Nesterov <oleg@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] clone3: validate stack arguments
Date: Thu, 31 Oct 2019 11:41:06 +0000 [thread overview]
Message-ID: <c600032527d24cf2a7dfd8a81467fd6f@AcuMS.aculab.com> (raw)
In-Reply-To: <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)
next prev parent reply other threads:[~2019-10-31 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 11:36 [PATCH] clone3: validate stack arguments Christian Brauner
2019-10-31 11:41 ` David Laight [this message]
2019-10-31 13:59 ` Aleksa Sarai
2019-10-31 14:27 ` David Laight
2019-10-31 16:46 ` Oleg Nesterov
2019-11-01 11:06 ` Christian Brauner
2019-11-01 12:32 ` Oleg Nesterov
2019-11-01 14:40 ` Christian Brauner
2019-11-01 14:57 ` Szabolcs Nagy
2019-11-01 15:10 ` Christian Brauner
2019-11-05 14:23 ` Arnd Bergmann
2019-11-05 20:23 ` Michael Kerrisk (man-pages)
[not found] ` <20191031124037.E26AF20650@mail.kernel.org>
2019-11-06 2:18 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c600032527d24cf2a7dfd8a81467fd6f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=dhowells@redhat.com \
--cc=fweimer@redhat.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).