From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Meredydd Luff <meredydd@senatehouse.org>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Ingo Molnar <mingo@redhat.com>, Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] [RFC] syscalls,x86: Add execveat() system call (v2)
Date: Thu, 09 Aug 2012 13:29:29 -0700 [thread overview]
Message-ID: <50241DA9.7070108@zytor.com> (raw)
In-Reply-To: <50240D47.7050906@amacapital.net>
On 08/09/2012 12:19 PM, Andy Lutomirski wrote:
> On 08/01/2012 03:10 PM, Meredydd Luff wrote:
>>
>> +#ifndef sys_execveat
>> +asmlinkage long sys_execveat(int dfd, const char __user *filename,
>> + const char __user *const __user *argv,
>> + const char __user *const __user *envp,
>> + struct pt_regs *regs);
>> +#endif
>
> Should this have a flags argument for future extension?
>
Not just for future extension. We already have a NOFOLLOW flag for the
-at functions, and that would be applicable here. CLOEXEC, obviously not ;)
-hpa
prev parent reply other threads:[~2012-08-09 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 22:10 [PATCH] [RFC] syscalls,x86: Add execveat() system call (v2) Meredydd Luff
2012-08-01 22:53 ` H. Peter Anvin
2012-08-01 23:09 ` Meredydd Luff
2012-08-01 23:30 ` H. Peter Anvin
2012-08-01 23:32 ` H. Peter Anvin
[not found] ` <CAD=T17GaEMU_PDDvaJ9GVRUtzTZ069AN2yTuX6=rVo6jNO+6oA@mail.gmail.com>
2012-08-02 0:52 ` H. Peter Anvin
2012-08-02 6:55 ` Al Viro
2012-08-02 9:14 ` Meredydd Luff
2012-08-02 10:30 ` Al Viro
2012-08-02 10:51 ` Meredydd Luff
2012-08-09 19:19 ` Andy Lutomirski
2012-08-09 20:29 ` H. Peter Anvin [this message]
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=50241DA9.7070108@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=meredydd@senatehouse.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
/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