From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
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 xfs tree
Date: Tue, 29 Oct 2019 10:11:51 +1100 [thread overview]
Message-ID: <20191029101151.54807d2f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 4096 bytes --]
Hi all,
After merging the xfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/compat_ioctl.c: In function '__do_compat_sys_ioctl':
fs/compat_ioctl.c:1056:2: error: case label not within a switch statement
1056 | case FICLONE:
| ^~~~
fs/compat_ioctl.c:1057:2: error: case label not within a switch statement
1057 | case FICLONERANGE:
| ^~~~
fs/compat_ioctl.c:1058:2: error: case label not within a switch statement
1058 | case FIDEDUPERANGE:
| ^~~~
fs/compat_ioctl.c:1059:2: error: case label not within a switch statement
1059 | case FS_IOC_FIEMAP:
| ^~~~
fs/compat_ioctl.c:1062:2: error: case label not within a switch statement
1062 | case FIBMAP:
| ^~~~
fs/compat_ioctl.c:1063:2: error: case label not within a switch statement
1063 | case FIGETBSZ:
| ^~~~
fs/compat_ioctl.c:1064:2: error: case label not within a switch statement
1064 | case FIONREAD:
| ^~~~
fs/compat_ioctl.c:1066:4: error: break statement not within loop or switch
1066 | break;
| ^~~~~
fs/compat_ioctl.c:1069:2: error: 'default' label not within a switch statement
1069 | default:
| ^~~~~~~
fs/compat_ioctl.c:1078:3: error: break statement not within loop or switch
1078 | break;
| ^~~~~
fs/compat_ioctl.c:1077:4: error: label 'do_ioctl' used but not defined
1077 | goto do_ioctl;
| ^~~~
fs/compat_ioctl.c:1073:5: error: label 'out_fput' used but not defined
1073 | goto out_fput;
| ^~~~
fs/compat_ioctl.c:1005:3: error: label 'out' used but not defined
1005 | goto out;
| ^~~~
fs/compat_ioctl.c:1079:2: warning: no return statement in function returning non-void [-Wreturn-type]
1079 | }
| ^
fs/compat_ioctl.c: At top level:
fs/compat_ioctl.c:1081:2: error: expected identifier or '(' before 'if'
1081 | if (compat_ioctl_check_table(XFORM(cmd)))
| ^~
fs/compat_ioctl.c:1084:2: warning: data definition has no type or storage class
1084 | error = do_ioctl_trans(cmd, arg, f.file);
| ^~~~~
fs/compat_ioctl.c:1084:2: error: type defaults to 'int' in declaration of 'error' [-Werror=implicit-int]
fs/compat_ioctl.c:1084:25: error: 'cmd' undeclared here (not in a function)
1084 | error = do_ioctl_trans(cmd, arg, f.file);
| ^~~
fs/compat_ioctl.c:1084:30: error: 'arg' undeclared here (not in a function)
1084 | error = do_ioctl_trans(cmd, arg, f.file);
| ^~~
fs/compat_ioctl.c:1084:35: error: 'f' undeclared here (not in a function); did you mean 'fd'?
1084 | error = do_ioctl_trans(cmd, arg, f.file);
| ^
| fd
fs/compat_ioctl.c:1085:2: error: expected identifier or '(' before 'if'
1085 | if (error == -ENOIOCTLCMD)
| ^~
fs/compat_ioctl.c:1088:2: error: expected identifier or '(' before 'goto'
1088 | goto out_fput;
| ^~~~
fs/compat_ioctl.c:1090:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before ':' token
1090 | found_handler:
| ^
fs/compat_ioctl.c:1092:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before ':' token
1092 | do_ioctl:
| ^
fs/compat_ioctl.c:1094:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before ':' token
1094 | out_fput:
| ^
fs/compat_ioctl.c:1096:5: error: expected '=', ',', ';', 'asm' or '__attribute__' before ':' token
1096 | out:
| ^
fs/compat_ioctl.c:1098:1: error: expected identifier or '(' before '}' token
1098 | }
| ^
fs/compat_ioctl.c:976:12: warning: 'compat_ioctl_check_table' defined but not used [-Wunused-function]
976 | static int compat_ioctl_check_table(unsigned int xcmd)
| ^~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
d5e20bfa0b77 ("fs: add generic UNRESVSP and ZERO_RANGE ioctl handlers")
I have used the xfs tree from next-20191028 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-10-28 23:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 23:11 Stephen Rothwell [this message]
2019-10-28 23:18 ` linux-next: build failure after merge of the xfs tree Darrick J. Wong
2019-10-29 5:56 ` Christoph Hellwig
2019-10-29 6:23 ` Stephen Rothwell
2019-10-29 6:32 ` Christoph Hellwig
[not found] <jZld0KWAlgFM0KGNf6_lm-4ZXRf4uFdfuPXGopJi8jUD3StPMObAqCIaJUvNZvyoyxrWEJus6A_a0yxRt7X0Eg==@protonmail.internalid>
2025-07-18 0:08 ` Stephen Rothwell
2025-07-18 8:30 ` Carlos Maiolino
2025-07-18 8:33 ` Christoph Hellwig
2025-07-18 8:45 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 22:04 Stephen Rothwell
2024-12-11 9:44 ` Carlos Maiolino
2024-12-11 21:41 ` Carlos Maiolino
2020-07-07 0:27 Stephen Rothwell
2019-07-01 1:12 Stephen Rothwell
2016-02-09 0:17 Stephen Rothwell
2016-02-09 0:30 ` Eric Sandeen
2016-02-09 0:41 ` Stephen Rothwell
2015-04-20 2:35 Stephen Rothwell
2013-04-29 1:29 Stephen Rothwell
2013-04-29 1:40 ` Dave Chinner
2013-04-30 18:36 ` Ben Myers
2012-05-10 3:01 Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:43 ` Ben Myers
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=20191029101151.54807d2f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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