Buildresult: linus/ppc64le_defconfig+NO_KVM/powerpc-gcc5 built on May 1 2018, 20:26
kisskb
Revisions
|
Branches
|
Compilers
|
Configs
|
Build Results
|
Build Failures
|
Status:
OK
Date/Time:
May 1 2018, 20:26
Duration:
0:02:51.996940
Builder:
ka2
Revision:
Merge tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux (
fff75eb2a08c2ac96404a2d79685668f3cf5a7a3)
Target:
linus/ppc64le_defconfig+NO_KVM/powerpc-gcc5
Branch:
linus
Compiler:
powerpc-gcc5
(powerpc64le-linux-gcc (GCC) 5.2.0)
Config:
ppc64le_defconfig+NO_KVM
(
download
)
Log:
Download original
Possible warnings (1)
WARNING: modpost: Found 3 section mismatch(es).
Full Log
# git rev-parse -q --verify fff75eb2a08c2ac96404a2d79685668f3cf5a7a3^{commit} fff75eb2a08c2ac96404a2d79685668f3cf5a7a3 already have revision, skipping fetch # git checkout -q -f -B kisskb fff75eb2a08c2ac96404a2d79685668f3cf5a7a3 # git clean -qxdf # < git log -1 # commit fff75eb2a08c2ac96404a2d79685668f3cf5a7a3 # Merge: 8188fc8 b4678df1 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Mon Apr 30 16:53:40 2018 -0700 # # Merge tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux # # Pull errseq infrastructure fix from Jeff Layton: # "The PostgreSQL developers recently had a spirited discussion about the # writeback error handling in Linux, and reached out to us about a # behavoir change to the code that bit them when the errseq_t changes # were merged. # # When we changed to using errseq_t for tracking writeback errors, we # lost the ability for an application to see a writeback error that # occurred before the open on which the fsync was issued. This was # problematic for PostgreSQL which offloads fsync calls to a completely # separate process from the DB writers. # # This patch restores that ability. If the errseq_t value in the inode # does not have the SEEN flag set, then we just return 0 for the sample. # That ensures that any recorded error is always delivered at least # once. # # Note that we might still lose the error if the inode gets evicted from # the cache before anything can reopen it, but that was the case before # errseq_t was merged. At LSF/MM we had some discussion about keeping # inodes with unreported writeback errors around in the cache for longer # (possibly indefinitely), but that's really a separate problem" # # * tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux: # errseq: Always report a writeback error once # < /opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux-gcc --version # < git log --format=%s --max-count=1 fff75eb2a08c2ac96404a2d79685668f3cf5a7a3 # < make -s -j 48 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- ppc64le_defconfig # Added to kconfig CONFIG_KVM_BOOK3S_64=n # Added to kconfig CONFIG_KVM=n # yes \n | make -s -j 48 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -s -j 48 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- WARNING: modpost: Found 3 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Completed OK # rm -rf /kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le # Build took: 0:02:51.996940
© Michael Ellerman 2006-2018.