# 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-mipsel-o32-full-2016.08-613-ge98b4dd/bin/mipsel-linux-gcc --version
# < git log --format=%s --max-count=1 fff75eb2a08c2ac96404a2d79685668f3cf5a7a3
# < make -s -j 20 ARCH=mips O=/kisskb/build/linus_mips-defconfig_mipsel CROSS_COMPILE=/opt/cross/kisskb/br-mipsel-o32-full-2016.08-613-ge98b4dd/bin/mipsel-linux-  defconfig
# make -s -j 20 ARCH=mips O=/kisskb/build/linus_mips-defconfig_mipsel CROSS_COMPILE=/opt/cross/kisskb/br-mipsel-o32-full-2016.08-613-ge98b4dd/bin/mipsel-linux-  
FIT description: Linux 4.17.0-rc3-gfff75eb
Created:         Tue May  1 20:45:10 2018
 Image 0 (kernel@0)
  Description:  Linux 4.17.0-rc3-gfff75eb
  Created:      Tue May  1 20:45:10 2018
  Type:         Kernel Image
  Compression:  gzip compressed
  Data Size:    4456675 Bytes = 4352.22 kB = 4.25 MB
  Architecture: MIPS
  OS:           Linux
  Load Address: 0x80100000
  Entry Point:  0x80890520
  Hash algo:    sha1
  Hash value:   5bd24ce029ed1e68bd26109c8415625a92cb8f58
 Image 1 (fdt@boston)
  Description:  img,boston Device Tree
  Created:      Tue May  1 20:45:10 2018
  Type:         Flat Device Tree
  Compression:  uncompressed
  Data Size:    3668 Bytes = 3.58 kB = 0.00 MB
  Architecture: MIPS
  Hash algo:    sha1
  Hash value:   569c37cc891ce1e1f3a193cb41cc691a5d2debb5
 Image 2 (fdt@ni169445)
  Description:  NI 169445 device tree
  Created:      Tue May  1 20:45:10 2018
  Type:         Flat Device Tree
  Compression:  uncompressed
  Data Size:    1871 Bytes = 1.83 kB = 0.00 MB
  Architecture: MIPS
  Hash algo:    sha1
  Hash value:   51b89b31605ee62038c8468c429af091dfc75ec7
 Default Configuration: 'conf@default'
 Configuration 0 (conf@default)
  Description:  Generic Linux kernel
  Kernel:       kernel@0
 Configuration 1 (conf@boston)
  Description:  Boston Linux kernel
  Kernel:       kernel@0
  FDT:          fdt@boston
 Configuration 2 (conf@ni169445)
  Description:  NI 169445 Linux Kernel
  Kernel:       kernel@0
  FDT:          fdt@ni169445
Completed OK
# rm -rf /kisskb/build/linus_mips-defconfig_mipsel
# Build took: 0:02:21.343910