From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: linux-next: build failure after merge of the file-locks tree
Date: Wed, 17 May 2017 10:27:52 +1000 [thread overview]
Message-ID: <20170517102752.3bd4da91@canb.auug.org.au> (raw)
Hi Jeff,
After merging the file-locks tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/fcntl.c: In function 'SYSC_fcntl64':
fs/fcntl.c:414:30: error: 'argp' undeclared (first use in this function)
if (copy_from_user(&flock, argp, sizeof(flock)))
^
fs/fcntl.c:414:30: note: each undeclared identifier is reported only once for each function it appears in
fs/fcntl.c:416:23: error: 'filp' undeclared (first use in this function)
err = fcntl_getlk64(filp, cmd, &flock);
^
Caused by commit
0416b792294c ("fs/locks: pass kernel struct flock to fcntl_getlk/setlk")
This build has BITS_PER_LONG == 32.
I have used the file-locks tree from next-20170516 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-05-17 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 0:27 Stephen Rothwell [this message]
2017-05-17 1:10 ` linux-next: build failure after merge of the file-locks tree Jeff Layton
2017-05-17 1:48 ` Stephen Rothwell
2017-05-17 12:32 ` Jeff Layton
2017-05-17 12:35 ` Stephen Rothwell
2017-05-17 23:45 ` Stephen Rothwell
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=20170517102752.3bd4da91@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--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).