From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: tony.luck@gmail.com, torvalds@linux-foundation.org,
xiyou.wangcong@gmail.com, ralf@linux-mips.org,
rmk+kernel@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix the declaration of sys_execve() in asm-generic/syscalls.h
Date: Wed, 18 Aug 2010 13:44:16 -0700 [thread overview]
Message-ID: <20100818134416.50403573.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100818175533.22912.89002.stgit@warthog.procyon.org.uk>
On Wed, 18 Aug 2010 18:55:33 +0100
David Howells <dhowells@redhat.com> wrote:
> Fix the declaration of sys_execve() in asm-generic/syscalls.h to have various
> consts applied to its pointers.
>
crappy changelog :(
> ---
>
> include/asm-generic/syscalls.h | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-generic/syscalls.h b/include/asm-generic/syscalls.h
> index df84e3b..d89dec8 100644
> --- a/include/asm-generic/syscalls.h
> +++ b/include/asm-generic/syscalls.h
> @@ -23,8 +23,10 @@ asmlinkage long sys_vfork(struct pt_regs *regs);
> #endif
>
> #ifndef sys_execve
> -asmlinkage long sys_execve(char __user *filename, char __user * __user *argv,
> - char __user * __user *envp, struct pt_regs *regs);
> +asmlinkage long sys_execve(const char __user *filename,
> + const char __user *const __user *argv,
> + const char __user *const __user *envp,
> + struct pt_regs *regs);
> #endif
>
> #ifndef sys_mmap2
Is this recent breakage?
In what way does the problem exhibit itself?
If we know these things we can then work out if the patch is needed in
2.6.36 and -stable.
prev parent reply other threads:[~2010-08-18 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 17:55 David Howells
2010-08-18 20:44 ` Andrew Morton [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=20100818134416.50403573.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tony.luck@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
/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
all inboxes | Powered by JetHome®