# git rev-parse -q --verify 96d4f267e40f9509e8a66e2b39e8b95655617693^{commit}
96d4f267e40f9509e8a66e2b39e8b95655617693
already have revision, skipping fetch
# git checkout -q -f -B kisskb 96d4f267e40f9509e8a66e2b39e8b95655617693
# git clean -qxdf
# < git log -1
# commit 96d4f267e40f9509e8a66e2b39e8b95655617693
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Thu Jan 3 18:57:57 2019 -0800
# 
#     Remove 'type' argument from access_ok() function
#     
#     Nobody has actually used the type (VERIFY_READ vs VERIFY_WRITE) argument
#     of the user address range verification function since we got rid of the
#     old racy i386-only code to walk page tables by hand.
#     
#     It existed because the original 80386 would not honor the write protect
#     bit when in kernel mode, so you had to do COW by hand before doing any
#     user access.  But we haven't supported that in a long time, and these
#     days the 'type' argument is a purely historical artifact.
#     
#     A discussion about extending 'user_access_begin()' to do the range
#     checking resulted this patch, because there is no way we're going to
#     move the old VERIFY_xyz interface to that model.  And it's best done at
#     the end of the merge window when I've done most of my merges, so let's
#     just get this done once and for all.
#     
#     This patch was mostly done with a sed-script, with manual fix-ups for
#     the cases that weren't of the trivial 'access_ok(VERIFY_xyz' form.
#     
#     There were a couple of notable cases:
#     
#      - csky still had the old "verify_area()" name as an alias.
#     
#      - the iter_iov code had magical hardcoded knowledge of the actual
#        values of VERIFY_{READ,WRITE} (not that they mattered, since nothing
#        really used it)
#     
#      - microblaze used the type argument for a debug printout
#     
#     but other than those oddities this should be a total no-op patch.
#     
#     I tried to fix up all architectures, did fairly extensive grepping for
#     access_ok() uses, and the changes are trivial, but I may have missed
#     something.  Any missed conversion should be trivially fixable, though.
#     
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-gcc --version
# < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-ld --version
# < git log --format=%s --max-count=1 96d4f267e40f9509e8a66e2b39e8b95655617693
# < make -s -j 8 ARCH=x86_64 O=/kisskb/build/linus-rand_x86_64-randconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-  randconfig
KCONFIG_SEED=0x79AFF61C
# Added to kconfig CONFIG_STANDALONE=y
# Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y
# Added to kconfig CONFIG_CC_STACKPROTECTOR_STRONG=n
# Added to kconfig CONFIG_GCC_PLUGINS=n
# Added to kconfig CONFIG_GCC_PLUGIN_CYC_COMPLEXITY=n
# Added to kconfig CONFIG_GCC_PLUGIN_SANCOV=n
# Added to kconfig CONFIG_GCC_PLUGIN_LATENT_ENTROPY=n
# yes \n | make -s -j 8 ARCH=x86_64 O=/kisskb/build/linus-rand_x86_64-randconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-  oldconfig
yes: standard output: Broken pipe
# make -s -j 8 ARCH=x86_64 O=/kisskb/build/linus-rand_x86_64-randconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-  
You are building kernel with non-retpoline compiler.
Please update your compiler.
make[1]: *** [arch/x86/Makefile:300: checkbin] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:152: sub-make] Error 2
Command 'make -s -j 8 ARCH=x86_64 O=/kisskb/build/linus-rand_x86_64-randconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-  ' returned non-zero exit status 2
# rm -rf /kisskb/build/linus-rand_x86_64-randconfig_um-x86_64
# Build took: 0:00:05.303510