# 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/br-xtensa-full-2016.08-613-ge98b4dd/bin/xtensa-linux-gcc --version
# < git log --format=%s --max-count=1 fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
# < make -s -j 48 ARCH=xtensa O=/kisskb/build/linus_xtensa-allnoconfig_xtensa CROSS_COMPILE=/opt/cross/kisskb/br-xtensa-full-2016.08-613-ge98b4dd/bin/xtensa-linux-  allnoconfig
drivers/staging/mt7621-dts/Kconfig:4:warning: 'BUILTIN_DTB' has wrong type. 'select' only accept arguments of bool and tristate type
# make -s -j 48 ARCH=xtensa O=/kisskb/build/linus_xtensa-allnoconfig_xtensa CROSS_COMPILE=/opt/cross/kisskb/br-xtensa-full-2016.08-613-ge98b4dd/bin/xtensa-linux-  
drivers/staging/mt7621-dts/Kconfig:4:warning: 'BUILTIN_DTB' has wrong type. 'select' only accept arguments of bool and tristate type
CONFIG_CC_STACKPROTECTOR_AUTO: Compiler does not support any known stack-protector
Completed OK
# rm -rf /kisskb/build/linus_xtensa-allnoconfig_xtensa
# Build took: 0:00:12.996262