Buildresult: linus-rand/arm64-randconfig/arm64-gcc8 built on Sep 21 2021, 10:13

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	Failed
Date/Time:	Sep 21 2021, 10:13
Duration:	0:04:13.558372
Builder:	blade4b
Revision:	Merge tag 'afs-fixes-20210913' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs (`d9fb678414c048e185eaddadd18d75f5e8832ff3)`
Target:	linus-rand/arm64-randconfig/arm64-gcc8
Branch:	linus-rand
Compiler:	arm64-gcc8 (aarch64-linux-gcc (GCC) 8.1.0 / GNU ld (GNU Binutils) 2.30)
Config:	randconfig (download)
Log:	Download original Possible errors scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" make[1]: * [Makefile:1183: vmlinux] Error 1 make: * [Makefile:219: __sub-make] Error 2 Possible warnings (3) .config:4133:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" Full Log # git rev-parse -q --verify d9fb678414c048e185eaddadd18d75f5e8832ff3^{commit} # git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master # git rev-parse -q --verify d9fb678414c048e185eaddadd18d75f5e8832ff3^{commit} d9fb678414c048e185eaddadd18d75f5e8832ff3 # git checkout -q -f -B kisskb d9fb678414c048e185eaddadd18d75f5e8832ff3 # git clean -qxdf # < git log -1 # commit d9fb678414c048e185eaddadd18d75f5e8832ff3 # Merge: 707a63e9a9dd 9d37e1cab2a9 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Mon Sep 20 15:49:02 2021 -0700 # # Merge tag 'afs-fixes-20210913' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs # # Pull AFS fixes from David Howells: # "Fixes for AFS problems that can cause data corruption due to # interaction with another client modifying data cached locally: # # - When d_revalidating a dentry, don't look at the inode to which it # points. Only check the directory to which the dentry belongs. This # was confusing things and causing the silly-rename cleanup code to # remove the file now at the dentry of a file that got deleted. # # - Fix mmap data coherency. When a callback break is received that # relates to a file that we have cached, the data content may have # been changed (there are other reasons, such as the user's rights # having been changed). However, we're checking it lazily, only on # entry to the kernel, which doesn't happen if we have a writeable # shared mapped page on that file. # # We make the kernel keep track of mmapped files and clear all PTEs # mapping to that file as soon as the callback comes in by calling # unmap_mapping_pages() (we don't necessarily want to zap the # pagecache). This causes the kernel to be reentered when userspace # tries to access the mmapped address range again - and at that point # we can query the server and, if we need to, zap the page cache. # # Ideally, I would check each file at the point of notification, but # that involves poking the server[] - which is holding an exclusive # lock on the vnode it is changing, waiting for all the clients it # notified to reply. This could then deadlock against the server. # Further, invalidating the pagecache might call ->launder_page(), # which would try to write to the file, which would definitely # deadlock. (AFS doesn't lease file access). # # [] Checking to see if the file content has changed is a matter of # comparing the current data version number, but we have to ask # the server for that. We also need to get a new callback promise # and we need to poke the server for that too. # # - Add some more points at which the inode is validated, since we're # doing it lazily, notably in ->read_iter() and ->page_mkwrite(), but # also when performing some directory operations. # # Ideally, checking in ->read_iter() would be done in some derivation # of filemap_read(). If we're going to call the server to read the # file, then we get the file status fetch as part of that. # # - The above is now causing us to make a lot more calls to # afs_validate() to check the inode - and afs_validate() takes the # RCU read lock each time to make a quick check (ie. # afs_check_validity()). This is entirely for the purpose of checking # cb_s_break to see if the server we're using reinitialised its list # of callbacks - however this isn't a very common event, so most of # the time we're taking this needlessly. # # Add a new cell-wide counter to count the number of # reinitialisations done by any server and check that - and only if # that changes, take the RCU read lock and check the server list (the # server list may change, but the cell a file is part of won't). # # - Don't update vnode->cb_s_break and ->cb_v_break inside the validity # checking loop. The cb_lock is done with read_seqretry, so we might # go round the loop a second time after resetting those values - and # that could cause someone else checking validity to miss something # (I think). # # Also included are patches for fixes for some bugs encountered whilst # debugging this: # # - Fix a leak of afs_read objects and fix a leak of keys hidden by # that. # # - Fix a leak of pages that couldn't be added to extend a writeback. # # - Fix the maintenance of i_blocks when i_size is changed by a local # write or a local dir edit" # # Link: https://bugzilla.kernel.org/show_bug.cgi?id=214217 [1] # Link: https://lore.kernel.org/r/163111665183.283156.17200205573146438918.stgit@warthog.procyon.org.uk/ # v1 # Link: https://lore.kernel.org/r/163113612442.352844.11162345591911691150.stgit@warthog.procyon.org.uk/ # i_blocks patch # # * tag 'afs-fixes-20210913' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs: # afs: Fix updating of i_blocks on file/dir extension # afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server # afs: Try to avoid taking RCU read lock when checking vnode validity # afs: Fix mmap coherency vs 3rd-party changes # afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation # afs: Add missing vnode validation checks # afs: Fix page leak # afs: Fix missing put on afs_read objects and missing get on the key therein # < /opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 d9fb678414c048e185eaddadd18d75f5e8832ff3 # < make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- randconfig # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # < make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- help # make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- olddefconfig .config:4133:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD # make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- MKDIR /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8/tools/bpf/resolve_btfids//libbpf MKDIR /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8/tools/bpf/resolve_btfids//libsubcmd /kisskb/src/scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" /kisskb/src/scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4: Warning (pci_device_reg): /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0" LINK resolve_btfids BTF: .tmp_vmlinux.btf: pahole (pahole) is not available Failed to generate BTF for vmlinux Try to disable CONFIG_DEBUG_INFO_BTF make[1]: * [/kisskb/src/Makefile:1183: vmlinux] Error 1 make: * [Makefile:219: __sub-make] Error 2 Command 'make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- ' returned non-zero exit status 2 # rm -rf /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc8 # Build took: 0:04:13.558372

© Michael Ellerman 2006-2018.