Re: linux-next: build failure after merge of the vfs tree

On Tue, Jan 05, 2021 at 09:36:16AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from arch/x86/include/asm/elf.h:8, > from include/linux/elf.h:6, >

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from arch/x86/include/asm/elf.h:8, from include/linux/elf.h:6, from include/linux/elfcore-compat.h:5, from

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Tue, 10 Nov 2020 19:00:36 + Al Viro wrote: > > On Tue, Oct 27, 2020 at 04:59:12AM +, Al Viro wrote: > > > I'll rebase that branch on top of sparc tree tomorrow (and eventually I'd > > like > > it to go through the sparc tree anyway). > > Done - sorry for disappearing ;-/

Re: linux-next: build failure after merge of the vfs tree

On Tue, Oct 27, 2020 at 04:59:12AM +, Al Viro wrote: > I'll rebase that branch on top of sparc tree tomorrow (and eventually I'd like > it to go through the sparc tree anyway). Done - sorry for disappearing ;-/

Re: linux-next: build failure after merge of the vfs tree

On Tue, Oct 27, 2020 at 03:14:14PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (sparc_defconfig) > failed like this: > > arch/sparc/lib/memset.S: Assembler messages: > arch/sparc/lib/memset.S:149: Error: Unknown opcode: `ext(12b, 13b,21f)' >

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (sparc_defconfig) failed like this: arch/sparc/lib/memset.S: Assembler messages: arch/sparc/lib/memset.S:149: Error: Unknown opcode: `ext(12b, 13b,21f)' Caused by commit 0e0bbae08a6e ("sparc32: switch __bzero() away from range

Re: linux-next: build failure after merge of the vfs tree

On Wed, Oct 07, 2020 at 08:04:05AM +1100, Stephen Rothwell wrote: > Hi Josh, > > On Tue, 6 Oct 2020 09:30:12 -0500 Josh Poimboeuf wrote: > > > > On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > >

Re: linux-next: build failure after merge of the vfs tree

Hi Josh, On Tue, 6 Oct 2020 09:30:12 -0500 Josh Poimboeuf wrote: > > On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > > be unpleasant in all existing callers... > > > > Sorry, I've been

Re: linux-next: build failure after merge of the vfs tree

On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > be unpleasant in all existing callers... > > Sorry, I've been traveling. I'd just vote for making it "r". > > array_index_nospec() is always called

Re: linux-next: build failure after merge of the vfs tree

On Fri, Sep 25, 2020 at 02:38:20PM +0100, Al Viro wrote: > On Fri, Sep 25, 2020 at 10:01:28PM +1000, Stephen Rothwell wrote: > > $ x86_64-linux-gnu-gcc --version > > x86_64-linux-gnu-gcc (Debian 10.2.0-9) 10.2.0 > > $ x86_64-linux-gnu-ld --version > > GNU ld (GNU Binutils for Debian) 2.35 > > > >

Re: linux-next: build failure after merge of the vfs tree

That is the crude fix, and it should work. I'd much rather make compat_iovec always available, though. Let me give that a spin.

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from arch/arm/include/asm/atomic.h:11, from include/linux/atomic.h:7, from include/linux/crypto.h:15, from

Re: linux-next: build failure after merge of the vfs tree

On Fri, Sep 25, 2020 at 10:01:28PM +1000, Stephen Rothwell wrote: > $ x86_64-linux-gnu-gcc --version > x86_64-linux-gnu-gcc (Debian 10.2.0-9) 10.2.0 > $ x86_64-linux-gnu-ld --version > GNU ld (GNU Binutils for Debian) 2.35 > > and the gcc plugins don't get built for the allnoconfig builds. > I

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Thu, 24 Sep 2020 21:08:07 +0100 Al Viro wrote: > > On Thu, Sep 24, 2020 at 06:30:38PM +1000, Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > arch/x86/include/asm/barrier.h: Assembler messages: > >

Re: linux-next: build failure after merge of the vfs tree

On Thu, Sep 24, 2020 at 06:30:38PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > arch/x86/include/asm/barrier.h: Assembler messages: > arch/x86/include/asm/barrier.h:41: Error: operand type mismatch

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) failed like this: arch/x86/include/asm/barrier.h: Assembler messages: arch/x86/include/asm/barrier.h:41: Error: operand type mismatch for `cmp' arch/x86/include/asm/barrier.h:41: Error: operand type mismatch for

Re: linux-next: build failure after merge of the vfs tree

On Wed, Jul 29, 2020 at 08:33:05AM +0200, Christoph Hellwig wrote: > Thanks, > > I've sent out a fixed version. #work.quota-compat and #for-next rebuilt (and pushed) with it...

Re: linux-next: build failure after merge of the vfs tree

Thanks, I've sent out a fixed version.

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from : In function 'signal_compat_build_tests', inlined from 'sigaction_compat_abi' at arch/x86/kernel/signal_compat.c:166:2: include/linux/compiler_types.h:313:38: error:

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (sparc defconfig) failed like this: arch/sparc/kernel/ptrace_32.c: In function 'setregs_set': arch/sparc/kernel/ptrace_32.c:271:2: error: 'ret' undeclared (first use in this function); did you mean 'net'? ret = user_regset_copyin(,

Re: linux-next: build failure after merge of the vfs tree

On 5/6/20 8:35 PM, Al Viro wrote: > On Thu, May 07, 2020 at 10:39:21AM +1000, Stephen Rothwell wrote: >> Hi all, >> >> After merging the vfs tree, today's linux-next build (arm >> multi_v7_defconfig) failed like this: >> >> fs/eventfd.c: In function 'eventfd_read': >> fs/eventfd.c:226:6: error:

Re: linux-next: build failure after merge of the vfs tree

On Thu, May 07, 2020 at 10:39:21AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > fs/eventfd.c: In function 'eventfd_read': > fs/eventfd.c:226:6: error: implicit declaration of function

linux-next: build failure after merge of the vfs tree

Hi all, After merging the vfs tree, today's linux-next build (arm multi_v7_defconfig) failed like this: fs/eventfd.c: In function 'eventfd_read': fs/eventfd.c:226:6: error: implicit declaration of function 'iov_iter_count' [-Werror=implicit-function-declaration] 226 | if (iov_iter_count(to)

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Wed, 2 Jan 2019 15:01:40 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/fs_context.c: In function 'logfc': > fs/fs_context.c:400:3: error: implicit declaration of function > 'vprintk_emit'; did

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) failed like this: fs/fs_context.c: In function 'logfc': fs/fs_context.c:400:3: error: implicit declaration of function 'vprintk_emit'; did you mean 'dev_printk_emit'? [-Werror=implicit-function-declaration]

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 09:21:20 + David Howells wrote: > > I think these changes should cover them all. Yep, that fixes the build for me, thanks. Tested-by: Stephen Rothwell -- Cheers, Stephen Rothwell pgpUP0DRJWa3r.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 09:21:20 + David Howells wrote: > > I think these changes should cover them all. Yep, that fixes the build for me, thanks. Tested-by: Stephen Rothwell -- Cheers, Stephen Rothwell pgpUP0DRJWa3r.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

I think these changes should cover them all. David --- diff --git a/samples/vfs/test-fs-query.c b/samples/vfs/test-fs-query.c index 511541d12b9e..4635bf1eb3d4 100644 --- a/samples/vfs/test-fs-query.c +++ b/samples/vfs/test-fs-query.c @@ -27,6 +27,13 @@ #include #include +#ifndef __NR_fsopen

Re: linux-next: build failure after merge of the vfs tree

I think these changes should cover them all. David --- diff --git a/samples/vfs/test-fs-query.c b/samples/vfs/test-fs-query.c index 511541d12b9e..4635bf1eb3d4 100644 --- a/samples/vfs/test-fs-query.c +++ b/samples/vfs/test-fs-query.c @@ -27,6 +27,13 @@ #include #include +#ifndef __NR_fsopen

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 15:33:34 +1100 Stephen Rothwell wrote: > > Hi Al, David, > > These have returned, so I have disabled CONFIG_SAMPLE_VFS again. Here is the current set of errors I git today (this is from a PowerPC allyesconfig build native compiler on a PowerPC64 LE machine):

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 15:33:34 +1100 Stephen Rothwell wrote: > > Hi Al, David, > > These have returned, so I have disabled CONFIG_SAMPLE_VFS again. Here is the current set of errors I git today (this is from a PowerPC allyesconfig build native compiler on a PowerPC64 LE machine):

Re: linux-next: build failure after merge of the vfs tree

Hi Al, David, These have returned, so I have disabled CONFIG_SAMPLE_VFS again. On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': >

Re: linux-next: build failure after merge of the vfs tree

Hi Al, David, These have returned, so I have disabled CONFIG_SAMPLE_VFS again. On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': >

Re: linux-next: build failure after merge of the vfs tree

Hi Jaegeuk, On Tue, 16 Oct 2018 09:37:44 -0700 Jaegeuk Kim wrote: > > I've modified this patch in f2fs tree to use SB_RDONLY. Thanks for that. -- Cheers, Stephen Rothwell pgpFgDa4GbUu9.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

Hi Jaegeuk, On Tue, 16 Oct 2018 09:37:44 -0700 Jaegeuk Kim wrote: > > I've modified this patch in f2fs tree to use SB_RDONLY. Thanks for that. -- Cheers, Stephen Rothwell pgpFgDa4GbUu9.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

On 10/16, Stephen Rothwell wrote: > Hi all, > > On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > >

Re: linux-next: build failure after merge of the vfs tree

On 10/16, Stephen Rothwell wrote: > Hi all, > > On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > >

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > /home/sfr/next/next/fs/f2fs/super.c:1589:16: error:

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > /home/sfr/next/next/fs/f2fs/super.c:1589:16: error:

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': /home/sfr/next/next/fs/f2fs/super.c:1589:16: error: 'MS_RDONLY' undeclared (first use in this function); did you mean 'IS_RDONLY'?

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': /home/sfr/next/next/fs/f2fs/super.c:1589:16: error: 'MS_RDONLY' undeclared (first use in this function); did you mean 'IS_RDONLY'?

Re: linux-next: build failure after merge of the vfs tree

Michael Ellerman wrote: > I realise these are in samples rather than selftests, but what most of > the selftests do is just #define the syscall number if it's not defined, > so that you're not dependent on getting the headers. The reason I don't want to do that is that syscall numbers aren't

Re: linux-next: build failure after merge of the vfs tree

Michael Ellerman wrote: > I realise these are in samples rather than selftests, but what most of > the selftests do is just #define the syscall number if it's not defined, > so that you're not dependent on getting the headers. The reason I don't want to do that is that syscall numbers aren't

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell writes: > Hi David, > > On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: >> >> Stephen Rothwell wrote: >> >> > > I think the problem is that I haven't allocated system call numbers for >> > > any arches other than x86 - even the x86 syscall numbers are provisional >> >

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell writes: > Hi David, > > On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: >> >> Stephen Rothwell wrote: >> >> > > I think the problem is that I haven't allocated system call numbers for >> > > any arches other than x86 - even the x86 syscall numbers are provisional >> >

Re: linux-next: build failure after merge of the vfs tree

David Howells writes: > Stephen Rothwell wrote: > >> > After merging the vfs tree, today's linux-next build (powerpc >> > allyesconfig) failed like this: >> > >> > samples/vfs/test-fsinfo.c: In function 'fsinfo': >> > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first >>

Re: linux-next: build failure after merge of the vfs tree

David Howells writes: > Stephen Rothwell wrote: > >> > After merging the vfs tree, today's linux-next build (powerpc >> > allyesconfig) failed like this: >> > >> > samples/vfs/test-fsinfo.c: In function 'fsinfo': >> > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first >>

Re: linux-next: build failure after merge of the vfs tree

On Wed, Sep 19, 2018 at 1:50 AM Stephen Rothwell wrote: > On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > > allyesconfig) failed like this: > > > > > > > > samples/vfs/test-fsinfo.c:

Re: linux-next: build failure after merge of the vfs tree

On Wed, Sep 19, 2018 at 1:50 AM Stephen Rothwell wrote: > On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > > allyesconfig) failed like this: > > > > > > > > samples/vfs/test-fsinfo.c:

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > I think the problem is that I haven't allocated system call numbers for > > > any arches other than x86 - even the x86 syscall numbers are provisional > > > until the patchset is taken

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > I think the problem is that I haven't allocated system call numbers for > > > any arches other than x86 - even the x86 syscall numbers are provisional > > > until the patchset is taken

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > I think the problem is that I haven't allocated system call numbers for > > any arches other than x86 - even the x86 syscall numbers are provisional > > until the patchset is taken upstream. I'm not sure of the best way to > > deal with this - make the samples

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > I think the problem is that I haven't allocated system call numbers for > > any arches other than x86 - even the x86 syscall numbers are provisional > > until the patchset is taken upstream. I'm not sure of the best way to > > deal with this - make the samples

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > allyesconfig) failed like this: > > > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > >

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > allyesconfig) failed like this: > > > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > >

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use > > in this function); did you

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use > > in this function); did you

Re: linux-next: build failure after merge of the vfs tree

Hi David, Al, On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared

Re: linux-next: build failure after merge of the vfs tree

Hi David, Al, On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (sparc64 defconfig) failed like this: In file included from arch/sparc/include/asm/fbio.h:5:0, from fs/compat_ioctl.c:76: arch/sparc/include/uapi/asm/fbio.h:100:25: error: field 'pos' has incomplete type

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (sparc64 defconfig) failed like this: In file included from arch/sparc/include/asm/fbio.h:5:0, from fs/compat_ioctl.c:76: arch/sparc/include/uapi/asm/fbio.h:100:25: error: field 'pos' has incomplete type

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc allyesconfig) failed like this: samples/vfs/test-fsinfo.c: In function 'fsinfo': samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use in this function); did you mean 'fsinfo'? return

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc allyesconfig) failed like this: samples/vfs/test-fsinfo.c: In function 'fsinfo': samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use in this function); did you mean 'fsinfo'? return

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc allyesconfig) failed like this: samples/mount_api/test-fsmount.c: In function 'fsopen': samples/mount_api/test-fsmount.c:63:17: error: '__NR_fsopen' undeclared (first use in this function); did you mean 'fsopen'? return

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc allyesconfig) failed like this: samples/mount_api/test-fsmount.c: In function 'fsopen': samples/mount_api/test-fsmount.c:63:17: error: '__NR_fsopen' undeclared (first use in this function); did you mean 'fsopen'? return

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powercp allyesconfig) failed like this (I have also included all the warnings): samples/statx/test-fsinfo.c: In function 'fsinfo': samples/statx/test-fsinfo.c:36:17: error: '__NR_fsinfo' undeclared (first use in this function); did

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powercp allyesconfig) failed like this (I have also included all the warnings): samples/statx/test-fsinfo.c: In function 'fsinfo': samples/statx/test-fsinfo.c:36:17: error: '__NR_fsinfo' undeclared (first use in this function); did

Re: linux-next: build failure after merge of the vfs tree

2018-08-07 9:59 GMT+09:00 Stephen Rothwell : > Hi all, > > On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell > wrote: >> >> On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell >> wrote: >> > >> > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) >> > failed like this:

Re: linux-next: build failure after merge of the vfs tree

2018-08-07 9:59 GMT+09:00 Stephen Rothwell : > Hi all, > > On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell > wrote: >> >> On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell >> wrote: >> > >> > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) >> > failed like this:

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /usr/bin/ld: /home/sfr/next/tmp/ccWnssuq.o: in function `dump_attr_TIMESTAMP_INFO': test-fsinfo.c:(.text+0x5d4): undefined reference to `pow' /usr/bin/ld: test-fsinfo.c:(.text+0x618): undefined

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /usr/bin/ld: /home/sfr/next/tmp/ccWnssuq.o: in function `dump_attr_TIMESTAMP_INFO': test-fsinfo.c:(.text+0x5d4): undefined reference to `pow' /usr/bin/ld: test-fsinfo.c:(.text+0x618): undefined

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell wrote: > > On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > samples/statx/test-fsinfo.c:26:10: fatal error:

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell wrote: > > On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > samples/statx/test-fsinfo.c:26:10: fatal error:

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > samples/statx/test-fsinfo.c:26:10: fatal error: linux/fsinfo.h: No such file > or directory > #include >

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > samples/statx/test-fsinfo.c:26:10: fatal error: linux/fsinfo.h: No such file > or directory > #include >

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: samples/statx/test-fsinfo.c:26:10: fatal error: linux/fsinfo.h: No such file or directory #include ^~~~ Caused by commit 90b413cb970a ("vfs: syscall: Add fsinfo() to

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) failed like this: samples/statx/test-fsinfo.c:26:10: fatal error: linux/fsinfo.h: No such file or directory #include ^~~~ Caused by commit 90b413cb970a ("vfs: syscall: Add fsinfo() to

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxlflash/ocxl_hw.c:62:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .mount = ocxlflash_fs_mount, ^~

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxlflash/ocxl_hw.c:62:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .mount = ocxlflash_fs_mount, ^~

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Sun, 8 Apr 2018 03:19:56 +0100 Al Viro wrote: > > > > Caused by commit > > > > > > 92afc556e622 ("buffer.c: call thaw_super during emergency thaw") > > > > > > I have reverted that commit for today. > > > > I am still doing that revert ... > > That's

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Sun, 8 Apr 2018 03:19:56 +0100 Al Viro wrote: > > > > Caused by commit > > > > > > 92afc556e622 ("buffer.c: call thaw_super during emergency thaw") > > > > > > I have reverted that commit for today. > > > > I am still doing that revert ... > > That's interesting, seeing that

Re: linux-next: build failure after merge of the vfs tree

On Tue, Apr 03, 2018 at 12:26:29PM +1000, Stephen Rothwell wrote: > Hi Al, > > On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > fs/super.c: In

Re: linux-next: build failure after merge of the vfs tree

On Tue, Apr 03, 2018 at 12:26:29PM +1000, Stephen Rothwell wrote: > Hi Al, > > On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > fs/super.c: In function

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function >

Re: linux-next: build failure after merge of the vfs tree

On Mon, Mar 19, 2018 at 05:06:27PM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function >

Re: linux-next: build failure after merge of the vfs tree

On Mon, Mar 19, 2018 at 05:06:27PM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function >

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) failed like this: fs/super.c: In function 'do_thaw_all_callback': fs/super.c:942:3: error: implicit declaration of function 'emergency_thaw_bdev'; did you mean 'emergency_remount'?

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) failed like this: fs/super.c: In function 'do_thaw_all_callback': fs/super.c:942:3: error: implicit declaration of function 'emergency_thaw_bdev'; did you mean 'emergency_remount'?

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'hva_to_pfn_slow': arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1379:35: error: 'start' undeclared (first use in this function)

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'hva_to_pfn_slow': arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1379:35: error: 'start' undeclared (first use in this function)

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > - if (inode->i_mode & S_IALLUGO != 0775) > + if ((inode->i_mode & S_IALLUGO) != 0775) Acked-by: David Howells

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > - if (inode->i_mode & S_IALLUGO != 0775) > + if ((inode->i_mode & S_IALLUGO) != 0775) Acked-by: David Howells

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:619:20: error: suggest parentheses around comparison in operand of '&'

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:619:20: error: suggest parentheses around comparison in operand of '&'

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jul 10, 2017 at 12:15:11PM +1000, Stephen Rothwell wrote: > Hi Al, > Caused by commit > > 4f9365d9e2e7 ("spufs: Implement show_options") Obvious incremental follows, will fold and push diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jul 10, 2017 at 12:15:11PM +1000, Stephen Rothwell wrote: > Hi Al, > Caused by commit > > 4f9365d9e2e7 ("spufs: Implement show_options") Obvious incremental follows, will fold and push diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:612:18: error: 'struct dentry' has no member named 'i_uid' if

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:612:18: error: 'struct dentry' has no member named 'i_uid' if

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > From: Stephen Rothwell > Date: Mon, 27 Feb 2017 11:21:47 +1100 > Subject: [PATCH] statx: disable the sample code for now > > Signed-off-by: Stephen Rothwell > --- > samples/Kconfig | 1 + > 1 file

  1   2   >