# git rev-parse -q --verify 0d3eb744aed40ffce820cded61d7eac515199165^{commit}
# git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master
warning: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

# git rev-parse -q --verify 0d3eb744aed40ffce820cded61d7eac515199165^{commit}
0d3eb744aed40ffce820cded61d7eac515199165
# git checkout -q -f -B kisskb 0d3eb744aed40ffce820cded61d7eac515199165
# git clean -qxdf
# < git log -1
# commit 0d3eb744aed40ffce820cded61d7eac515199165
# Merge: dfc191544864 5da7cb193db3
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Mon Apr 10 14:15:17 2023 -0700
# 
#     Merge tag 'urgent-rcu.2023.04.07a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
#     
#     Pull RCU fix from Paul McKenney:
#      "This fixes a pair of bugs in which an improbable but very real
#       sequence of events can cause kfree_rcu() to be a bit too quick about
#       freeing the memory passed to it.
#     
#       It turns out that this pair of bugs is about two years old, and so
#       this is not a v6.3 regression. However: (1) It just started showing up
#       in the wild and (2) Its consequences are dire, so its fix needs to go
#       in sooner rather than later.
#     
#       Testing is of course being upgraded, and the upgraded tests detect
#       this situation very quickly. But to the best of my knowledge right
#       now, the tests are not particularly urgent and will thus most likely
#       show up in the v6.5 merge window (the one after this coming one).
#     
#       Kudos to Ziwei Dai and his group for tracking this one down the hard
#       way!"
#     
#     * tag 'urgent-rcu.2023.04.07a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu:
#       rcu/kvfree: Avoid freeing new kfree_rcu() memory after old grace period
# < /opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-gcc --version
# < /opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-ld --version
# < git log --format=%s --max-count=1 0d3eb744aed40ffce820cded61d7eac515199165
# < make -s -j 160 ARCH=sparc64 O=/kisskb/build/linus_sparc64-defconfig_sparc64-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-  defconfig
# < make -s -j 160 ARCH=sparc64 O=/kisskb/build/linus_sparc64-defconfig_sparc64-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-  help
# make -s -j 160 ARCH=sparc64 O=/kisskb/build/linus_sparc64-defconfig_sparc64-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-  olddefconfig
# make -s -j 160 ARCH=sparc64 O=/kisskb/build/linus_sparc64-defconfig_sparc64-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/sparc64-linux/bin/sparc64-linux-  
<stdin>:1519:2: warning: #warning syscall clone3 not implemented [-Wcpp]
WARNING: modpost: EXPORT symbol "_mcount" [vmlinux] version generation failed, symbol will not be versioned.
Is "_mcount" prototyped in <asm/asm-prototypes.h>?
  kernel: arch/sparc/boot/image is ready
  kernel: arch/sparc/boot/zImage is ready
Completed OK
# rm -rf /kisskb/build/linus_sparc64-defconfig_sparc64-gcc11
# Build took: 0:01:02.437047