From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <christian@brauner.io>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the pidfd tree
Date: Thu, 28 Mar 2019 13:04:49 +1100 [thread overview]
Message-ID: <20190328130449.1b6334b6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]
Hi Christian,
After merging the pidfd tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
kernel/pid.c: In function '__do_sys_pidfd_open':
kernel/pid.c:652:7: error: 'fd' redeclared as different kind of symbol
long fd = -EINVAL;
^~
In file included from kernel/pid.c:40:
kernel/pid.c:649:46: note: previous definition of 'fd' was here
SYSCALL_DEFINE4(pidfd_open, pid_t, pid, int, fd, int, pidfd,
~~~~~^~
include/linux/syscalls.h:117:27: note: in definition of macro '__SC_DECL'
#define __SC_DECL(t, a) t a
^
include/linux/syscalls.h:112:35: note: in expansion of macro '__MAP3'
#define __MAP4(m,t,a,...) m(t,a), __MAP3(m,__VA_ARGS__)
^~~~~~
include/linux/syscalls.h:115:22: note: in expansion of macro '__MAP4'
#define __MAP(n,...) __MAP##n(__VA_ARGS__)
^~~~~
include/linux/syscalls.h:253:36: note: in expansion of macro '__MAP'
static inline long __do_sys##name(__MAP(x,__SC_DECL,__VA_ARGS__))
^~~~~
include/linux/syscalls.h:226:2: note: in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^~~~~~~~~~~~~~~~~
include/linux/syscalls.h:218:36: note: in expansion of macro 'SYSCALL_DEFINEx'
#define SYSCALL_DEFINE4(name, ...) SYSCALL_DEFINEx(4, _##name, __VA_ARGS__)
^~~~~~~~~~~~~~~
kernel/pid.c:649:1: note: in expansion of macro 'SYSCALL_DEFINE4'
SYSCALL_DEFINE4(pidfd_open, pid_t, pid, int, fd, int, pidfd,
^~~~~~~~~~~~~~~
kernel/pid.c:663:7: error: 'procfd' undeclared (first use in this function); did you mean 'pidfd'?
if (procfd != -1 || pidfd != -1)
^~~~~~
pidfd
kernel/pid.c:663:7: note: each undeclared identifier is reported only once for each function it appears in
Caused by commit
9170fba40db0 ("pid: add pidfd_open()")
I have used the version of the pifd tree from next-20190327 for today.
Please do *not* use linux-next as a development tree (I have seen several
different version of this code over the past few days :-(). The rules
for linux-next included code include:
"
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch)."
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-03-28 2:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 2:04 Stephen Rothwell [this message]
2019-03-28 2:28 ` linux-next: build failure after merge of the pidfd tree Christian Brauner
2019-03-28 2:57 ` Stephen Rothwell
2020-05-12 10:18 Stephen Rothwell
2020-05-12 10:20 ` Christian Brauner
2020-05-12 10:28 ` 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=20190328130449.1b6334b6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).