From: Josh Triplett <josh@joshtriplett.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 187/255] arch/s390/kernel/compat_wrapper.c:205:7: error: conflicting types for 'sys_clone'
Date: Wed, 13 May 2015 21:19:41 -0700 [thread overview]
Message-ID: <20150514041941.GA26568@x> (raw)
In-Reply-To: <201505141011.OB8iS79o%fengguang.wu@intel.com>
On Thu, May 14, 2015 at 10:22:13AM +0800, kbuild test robot wrote:
> >> arch/s390/kernel/compat_wrapper.c:205:7: error: conflicting types for 'sys_clone'
> COMPAT_SYSCALL_WRAP5(clone, unsigned long, newsp, unsigned long, clone_flags, int __user *, parent_tidptr, int __user *, child_tidptr, int, tls_val);
> ^
> In file included from arch/s390/kernel/compat_wrapper.c:7:0:
> include/linux/syscalls.h:837:7: note: previous declaration of 'sys_clone' was here
> asmlinkage long sys_clone(unsigned long, unsigned long, int __user *,
> ^
>
> vim +/sys_clone +205 arch/s390/kernel/compat_wrapper.c
>
> 7f6afe87a arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 199 COMPAT_SYSCALL_WRAP2(pipe2, int __user *, fildes, int, flags);
> 7f6afe87a arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 200 COMPAT_SYSCALL_WRAP3(dup3, unsigned int, oldfd, unsigned int, newfd, int, flags);
> 7f6afe87a arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 201 COMPAT_SYSCALL_WRAP1(epoll_create1, int, flags);
> 7f6afe87a arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 202 COMPAT_SYSCALL_WRAP2(tkill, int, pid, int, sig);
> 7f6afe87a arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 203 COMPAT_SYSCALL_WRAP3(tgkill, int, tgid, int, pid, int, sig);
> ab4f8bba1 arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 204 COMPAT_SYSCALL_WRAP5(perf_event_open, struct perf_event_attr __user *, attr_uptr, pid_t, pid, int, cpu, int, group_fd, unsigned long, flags);
> ab4f8bba1 arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 @205 COMPAT_SYSCALL_WRAP5(clone, unsigned long, newsp, unsigned long, clone_flags, int __user *, parent_tidptr, int __user *, child_tidptr, int, tls_val);
> 00fcb1494 arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 206 COMPAT_SYSCALL_WRAP2(fanotify_init, unsigned int, flags, unsigned int, event_f_flags);
> 00fcb1494 arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 207 COMPAT_SYSCALL_WRAP4(prlimit64, pid_t, pid, unsigned int, resource, const struct rlimit64 __user *, new_rlim, struct rlimit64 __user *, old_rlim);
> 00fcb1494 arch/s390/kernel/compat_wrap.c Heiko Carstens 2014-03-01 208 COMPAT_SYSCALL_WRAP5(name_to_handle_at, int, dfd, const char __user *, name, struct file_handle __user *, handle, int __user *, mnt_id, int, flag);
I had no idea s390 had duplicate prototypes for syscalls. That's all
kinds of awful. Obvious incremental patch for -mm:
----- 8< -----
prev parent reply other threads:[~2015-05-14 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 2:22 [mmotm:master 187/255] arch/s390/kernel/compat_wrapper.c:205:7: error: conflicting types for 'sys_clone' kbuild test robot
2015-05-14 4:19 ` Josh Triplett [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=20150514041941.GA26568@x \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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).