# git gc
Expanding reachable commits in commit graph: 51813
Expanding reachable commits in commit graph: 107364
Expanding reachable commits in commit graph: 162596
Expanding reachable commits in commit graph: 221062
Expanding reachable commits in commit graph: 275053
Expanding reachable commits in commit graph: 333903
Expanding reachable commits in commit graph: 393041
Expanding reachable commits in commit graph: 453733
Expanding reachable commits in commit graph: 514196
Expanding reachable commits in commit graph: 566736
Expanding reachable commits in commit graph: 630288
Expanding reachable commits in commit graph: 693351
Expanding reachable commits in commit graph: 757688
Expanding reachable commits in commit graph: 823759
Expanding reachable commits in commit graph: 891711
Expanding reachable commits in commit graph: 960408
Expanding reachable commits in commit graph: 1030564
Expanding reachable commits in commit graph: 1078861
Expanding reachable commits in commit graph: 1151435
Expanding reachable commits in commit graph: 1225156
Expanding reachable commits in commit graph: 1235056, done.
Finding extra edges in commit graph:  61% (765295/1235056)
Finding extra edges in commit graph:  62% (765735/1235056)
Finding extra edges in commit graph:  63% (778086/1235056)
Finding extra edges in commit graph:  64% (790436/1235056)
Finding extra edges in commit graph:  65% (802787/1235056)
Finding extra edges in commit graph:  66% (815137/1235056)
Finding extra edges in commit graph:  67% (827488/1235056)
Finding extra edges in commit graph:  68% (839839/1235056)
Finding extra edges in commit graph:  69% (852189/1235056)
Finding extra edges in commit graph:  70% (864540/1235056)
Finding extra edges in commit graph:  71% (876890/1235056)
Finding extra edges in commit graph:  72% (889241/1235056)
Finding extra edges in commit graph:  73% (901591/1235056)
Finding extra edges in commit graph:  74% (913942/1235056)
Finding extra edges in commit graph:  75% (926292/1235056)
Finding extra edges in commit graph:  76% (938643/1235056)
Finding extra edges in commit graph:  77% (950994/1235056)
Finding extra edges in commit graph:  78% (963344/1235056)
Finding extra edges in commit graph:  79% (975695/1235056)
Finding extra edges in commit graph:  80% (988045/1235056)
Finding extra edges in commit graph:  81% (1000396/1235056)
Finding extra edges in commit graph:  82% (1012746/1235056)
Finding extra edges in commit graph:  83% (1025097/1235056)
Finding extra edges in commit graph:  84% (1037448/1235056)
Finding extra edges in commit graph:  85% (1049798/1235056)
Finding extra edges in commit graph:  86% (1062149/1235056)
Finding extra edges in commit graph:  87% (1074499/1235056)
Finding extra edges in commit graph:  88% (1086850/1235056)
Finding extra edges in commit graph:  89% (1099200/1235056)
Finding extra edges in commit graph:  90% (1111551/1235056)
Finding extra edges in commit graph:  91% (1123901/1235056)
Finding extra edges in commit graph:  92% (1136252/1235056)
Finding extra edges in commit graph:  93% (1148603/1235056)
Finding extra edges in commit graph:  94% (1160953/1235056)
Finding extra edges in commit graph:  95% (1173304/1235056)
Finding extra edges in commit graph:  96% (1185654/1235056)
Finding extra edges in commit graph:  97% (1198005/1235056)
Finding extra edges in commit graph:  98% (1210355/1235056)
Finding extra edges in commit graph:  99% (1222706/1235056)
Finding extra edges in commit graph: 100% (1235056/1235056)
Finding extra edges in commit graph: 100% (1235056/1235056), done.
Writing out commit graph in 4 passes:  54% (2702826/4940224)
Writing out commit graph in 4 passes:  55% (2717124/4940224)
Writing out commit graph in 4 passes:  56% (2766526/4940224)
Writing out commit graph in 4 passes:  57% (2815928/4940224)
Writing out commit graph in 4 passes:  58% (2865330/4940224)
Writing out commit graph in 4 passes:  59% (2914733/4940224)
Writing out commit graph in 4 passes:  60% (2964135/4940224)
Writing out commit graph in 4 passes:  61% (3013537/4940224)
Writing out commit graph in 4 passes:  61% (3040002/4940224)
Writing out commit graph in 4 passes:  62% (3062939/4940224)
Writing out commit graph in 4 passes:  63% (3112342/4940224)
Writing out commit graph in 4 passes:  64% (3161744/4940224)
Writing out commit graph in 4 passes:  65% (3211146/4940224)
Writing out commit graph in 4 passes:  66% (3260548/4940224)
Writing out commit graph in 4 passes:  67% (3309951/4940224)
Writing out commit graph in 4 passes:  68% (3359353/4940224)
Writing out commit graph in 4 passes:  68% (3376915/4940224)
Writing out commit graph in 4 passes:  69% (3408755/4940224)
Writing out commit graph in 4 passes:  70% (3458157/4940224)
Writing out commit graph in 4 passes:  71% (3507560/4940224)
Writing out commit graph in 4 passes:  72% (3556962/4940224)
Writing out commit graph in 4 passes:  73% (3606364/4940224)
Writing out commit graph in 4 passes:  74% (3655766/4940224)
Writing out commit graph in 4 passes:  75% (3705168/4940224)
Writing out commit graph in 4 passes:  76% (3754571/4940224)
Writing out commit graph in 4 passes:  77% (3803973/4940224)
Writing out commit graph in 4 passes:  77% (3847304/4940224)
Writing out commit graph in 4 passes:  78% (3853375/4940224)
Writing out commit graph in 4 passes:  79% (3902777/4940224)
Writing out commit graph in 4 passes:  80% (3952180/4940224)
Writing out commit graph in 4 passes:  81% (4001582/4940224)
Writing out commit graph in 4 passes:  82% (4050984/4940224)
Writing out commit graph in 4 passes:  83% (4100386/4940224)
Writing out commit graph in 4 passes:  84% (4149789/4940224)
Writing out commit graph in 4 passes:  85% (4199191/4940224)
Writing out commit graph in 4 passes:  86% (4248593/4940224)
Writing out commit graph in 4 passes:  87% (4297995/4940224)
Writing out commit graph in 4 passes:  88% (4347398/4940224)
Writing out commit graph in 4 passes:  89% (4396800/4940224)
Writing out commit graph in 4 passes:  90% (4446202/4940224)
Writing out commit graph in 4 passes:  91% (4495604/4940224)
Writing out commit graph in 4 passes:  92% (4545007/4940224)
Writing out commit graph in 4 passes:  93% (4594409/4940224)
Writing out commit graph in 4 passes:  94% (4643811/4940224)
Writing out commit graph in 4 passes:  95% (4693213/4940224)
Writing out commit graph in 4 passes:  96% (4742616/4940224)
Writing out commit graph in 4 passes:  97% (4792018/4940224)
Writing out commit graph in 4 passes:  98% (4841420/4940224)
Writing out commit graph in 4 passes:  99% (4890822/4940224)
Writing out commit graph in 4 passes: 100% (4940224/4940224)
Writing out commit graph in 4 passes: 100% (4940224/4940224), done.
# git rev-parse -q --verify 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf^{commit}
# git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master
# git rev-parse -q --verify 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf^{commit}
3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
# git checkout -q -f -B kisskb 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
# git clean -qxdf
# < git log -1
# commit 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
# Merge: c8e97fc6b4c0 712292308af2
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Sat Dec 16 10:40:51 2023 -0800
# 
#     Merge tag 'trace-v6.7-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
#     
#     Pull tracing fixes from Steven Rostedt:
#     
#      - Fix eventfs to check creating new files for events with names greater
#        than NAME_MAX. The eventfs lookup needs to check the return result of
#        simple_lookup().
#     
#      - Fix the ring buffer to check the proper max data size. Events must be
#        able to fit on the ring buffer sub-buffer, if it cannot, then it
#        fails to be written and the logic to add the event is avoided. The
#        code to check if an event can fit failed to add the possible absolute
#        timestamp which may make the event not be able to fit. This causes
#        the ring buffer to go into an infinite loop trying to find a
#        sub-buffer that would fit the event. Luckily, there's a check that
#        will bail out if it looped over a 1000 times and it also warns.
#     
#        The real fix is not to add the absolute timestamp to an event that is
#        starting at the beginning of a sub-buffer because it uses the
#        sub-buffer timestamp.
#     
#        By avoiding the timestamp at the start of the sub-buffer allows
#        events that pass the first check to always find a sub-buffer that it
#        can fit on.
#     
#      - Have large events that do not fit on a trace_seq to print "LINE TOO
#        BIG" like it does for the trace_pipe instead of what it does now
#        which is to silently drop the output.
#     
#      - Fix a memory leak of forgetting to free the spare page that is saved
#        by a trace instance.
#     
#      - Update the size of the snapshot buffer when the main buffer is
#        updated if the snapshot buffer is allocated.
#     
#      - Fix ring buffer timestamp logic by removing all the places that tried
#        to put the before_stamp back to the write stamp so that the next
#        event doesn't add an absolute timestamp. But each of these updates
#        added a race where by making the two timestamp equal, it was
#        validating the write_stamp so that it can be incorrectly used for
#        calculating the delta of an event.
#     
#      - There's a temp buffer used for printing the event that was using the
#        event data size for allocation when it needed to use the size of the
#        entire event (meta-data and payload data)
#     
#      - For hardening, use "%.*s" for printing the trace_marker output, to
#        limit the amount that is printed by the size of the event. This was
#        discovered by development that added a bug that truncated the '\0'
#        and caused a crash.
#     
#      - Fix a use-after-free bug in the use of the histogram files when an
#        instance is being removed.
#     
#      - Remove a useless update in the rb_try_to_discard of the write_stamp.
#        The before_stamp was already changed to force the next event to add
#        an absolute timestamp that the write_stamp is not used. But the
#        write_stamp is modified again using an unneeded 64-bit cmpxchg.
#     
#      - Fix several races in the 32-bit implementation of the
#        rb_time_cmpxchg() that does a 64-bit cmpxchg.
#     
#      - While looking at fixing the 64-bit cmpxchg, I noticed that because
#        the ring buffer uses normal cmpxchg, and this can be done in NMI
#        context, there's some architectures that do not have a working
#        cmpxchg in NMI context. For these architectures, fail recording
#        events that happen in NMI context.
#     
#     * tag 'trace-v6.7-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
#       ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI
#       ring-buffer: Have rb_time_cmpxchg() set the msb counter too
#       ring-buffer: Fix 32-bit rb_time_read() race with rb_time_cmpxchg()
#       ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs
#       ring-buffer: Remove useless update to write_stamp in rb_try_to_discard()
#       ring-buffer: Do not try to put back write_stamp
#       tracing: Fix uaf issue when open the hist or hist_debug file
#       tracing: Add size check when printing trace_marker output
#       ring-buffer: Have saved event hold the entire event
#       ring-buffer: Do not update before stamp when switching sub-buffers
#       tracing: Update snapshot buffer on resize if it is allocated
#       ring-buffer: Fix memory leak of free page
#       eventfs: Fix events beyond NAME_MAX blocking tasks
#       tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
#       ring-buffer: Fix writing to the buffer with max_data_size
# < /opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-gcc --version
# < /opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-ld --version
# < git log --format=%s --max-count=1 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
# make -s -j 24 ARCH=sparc O=/kisskb/build/linus_defconfig_sparc64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-  defconfig
# < make -s -j 24 ARCH=sparc O=/kisskb/build/linus_defconfig_sparc64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-  help
# make -s -j 24 ARCH=sparc O=/kisskb/build/linus_defconfig_sparc64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-  olddefconfig
# make -s -j 24 ARCH=sparc O=/kisskb/build/linus_defconfig_sparc64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/sparc64-linux/bin/sparc64-linux-  
<stdin>:1519:2: warning: #warning syscall clone3 not implemented [-Wcpp]
  kernel: arch/sparc/boot/image is ready
  kernel: arch/sparc/boot/zImage is ready
Completed OK
# rm -rf /kisskb/build/linus_defconfig_sparc64-gcc12
# Build took: 0:07:27.146942