Buildresult: linus/or1ksim_defconfig/or32-gcc9 built on May 1 2018, 20:09

kisskb

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

Status:	OK
Date/Time:	May 1 2018, 20:09
Duration:	0:00:22.133868
Builder:	ka1
Revision:	Merge tag 'errseq-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux (`fff75eb2a08c2ac96404a2d79685668f3cf5a7a3)`
Target:	linus/or1ksim_defconfig/or32-gcc9
Branch:	linus
Compiler:	or32-gcc9 (or1k-linux-gcc (GCC) 5.4.0)
Config:	or1ksim_defconfig (download)
Log:	Download original No warnings found in log. 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/or1k-linux-5.4.0-20170218/or1k-linux/bin/or1k-linux-gcc --version # < git log --format=%s --max-count=1 fff75eb2a08c2ac96404a2d79685668f3cf5a7a3 # < make -s -j 48 ARCH=openrisc O=/kisskb/build/linus_or1ksim_defconfig_or32 CROSS_COMPILE=/opt/cross/kisskb/or1k-linux-5.4.0-20170218/or1k-linux/bin/or1k-linux- or1ksim_defconfig # make -s -j 48 ARCH=openrisc O=/kisskb/build/linus_or1ksim_defconfig_or32 CROSS_COMPILE=/opt/cross/kisskb/or1k-linux-5.4.0-20170218/or1k-linux/bin/or1k-linux- Completed OK # rm -rf /kisskb/build/linus_or1ksim_defconfig_or32 # Build took: 0:00:22.133868

© Michael Ellerman 2006-2018.