# git rev-parse -q --verify af0c9af1b3f66052c369d08be3f60fa9a9559e48^{commit}
af0c9af1b3f66052c369d08be3f60fa9a9559e48
already have revision, skipping fetch
# git checkout -q -f -B kisskb af0c9af1b3f66052c369d08be3f60fa9a9559e48
# git clean -qxdf
# < git log -1
# commit af0c9af1b3f66052c369d08be3f60fa9a9559e48
# Author: Waiman Long <longman@redhat.com>
# Date:   Wed Jan 30 13:52:38 2019 -0500
# 
#     fs/dcache: Track & report number of negative dentries
#     
#     The current dentry number tracking code doesn't distinguish between
#     positive & negative dentries.  It just reports the total number of
#     dentries in the LRU lists.
#     
#     As excessive number of negative dentries can have an impact on system
#     performance, it will be wise to track the number of positive and
#     negative dentries separately.
#     
#     This patch adds tracking for the total number of negative dentries in
#     the system LRU lists and reports it in the 5th field in the
#     /proc/sys/fs/dentry-state file.  The number, however, does not include
#     negative dentries that are in flight but not in the LRU yet as well as
#     those in the shrinker lists which are on the way out anyway.
#     
#     The number of positive dentries in the LRU lists can be roughly found by
#     subtracting the number of negative dentries from the unused count.
#     
#     Matthew Wilcox had confirmed that since the introduction of the
#     dentry_stat structure in 2.1.60, the dummy array was there, probably for
#     future extension.  They were not replacements of pre-existing fields.
#     So no sane applications that read the value of /proc/sys/fs/dentry-state
#     will do dummy thing if the last 2 fields of the sysctl parameter are not
#     zero.  IOW, it will be safe to use one of the dummy array entry for
#     negative dentry count.
#     
#     Signed-off-by: Waiman Long <longman@redhat.com>
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc --version
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld --version
# < git log --format=%s --max-count=1 af0c9af1b3f66052c369d08be3f60fa9a9559e48
# < make -s -j 24 ARCH=arm O=/kisskb/build/linus_h5000_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-  h5000_defconfig
# make -s -j 24 ARCH=arm O=/kisskb/build/linus_h5000_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-  
/kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl':
/kisskb/src/kernel/printk/printk.c:186:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/fs/proc/inode.c: In function 'proc_reg_open':
/kisskb/src/include/linux/list.h:65:12: warning: 'pdeo' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/fs/proc/inode.c:339:21: note: 'pdeo' was declared here
/kisskb/src/net/ipv4/ip_output.c: In function '__ip_append_data':
/kisskb/src/include/linux/skbuff.h:1338:6: warning: 'extra_uref' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/net/ipv4/ip_output.c:885:14: note: 'extra_uref' was declared here
Completed OK
# rm -rf /kisskb/build/linus_h5000_defconfig_arm
# Build took: 0:00:24.398103