* Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression
From: Christoph Hellwig @ 2026-07-15 14:53 UTC (permalink / raw)
To: Tetsuo Handa
Cc: Christoph Hellwig, kernel test robot, oe-lkp, lkp, linux-block,
linux-fsdevel, Mark Brown, linux-next, axboe
In-Reply-To: <4ea4703c-7385-4f75-aee2-f21a6c8cce82@I-love.SAKURA.ne.jp>
On Wed, Jul 15, 2026 at 11:45:41PM +0900, Tetsuo Handa wrote:
> On 2026/07/15 23:30, Christoph Hellwig wrote:
> > It's also a patch that has never been added to the maintainer
> > tree for goot reson. Tetsuo keeps doing this, so can we please
> > stop including their trees in linux-next as there seems to be
> > no other way to stop this?
>
> Then, can we please keep discussion on
> https://syzkaller.appspot.com/bug?extid=cd8a9a308e879a4e2c28 alive?
> I am asking Al Viro to reproduce xfs/259 problem, but it seems that
> Al is too busy to respond. I can drop this patch if somebody is
> interested in fixing this bug which became visible in 7.1. Current
> state is a result of insufficient interests/resources for debugging.
Not my business. But adding random patches affecting other subsystems
without any buy in is a no-go. Doing this repeatedly after beeing
reminded not to do it and for multiple subsystems is a red flag.
^ permalink raw reply
* Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression
From: Tetsuo Handa @ 2026-07-15 14:45 UTC (permalink / raw)
To: Christoph Hellwig, kernel test robot
Cc: oe-lkp, lkp, linux-block, linux-fsdevel, Mark Brown, linux-next,
axboe
In-Reply-To: <aleZammRRSVN4dl0@infradead.org>
On 2026/07/15 23:30, Christoph Hellwig wrote:
> It's also a patch that has never been added to the maintainer
> tree for goot reson. Tetsuo keeps doing this, so can we please
> stop including their trees in linux-next as there seems to be
> no other way to stop this?
Then, can we please keep discussion on
https://syzkaller.appspot.com/bug?extid=cd8a9a308e879a4e2c28 alive?
I am asking Al Viro to reproduce xfs/259 problem, but it seems that
Al is too busy to respond. I can drop this patch if somebody is
interested in fixing this bug which became visible in 7.1. Current
state is a result of insufficient interests/resources for debugging.
^ permalink raw reply
* Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression
From: Christoph Hellwig @ 2026-07-15 14:30 UTC (permalink / raw)
To: kernel test robot
Cc: Tetsuo Handa, oe-lkp, lkp, linux-block, linux-fsdevel, Mark Brown,
linux-next, axboe
In-Reply-To: <202607151655.9d74999d-lkp@intel.com>
It's also a patch that has never been added to the maintainer
tree for goot reson. Tetsuo keeps doing this, so can we please
stop including their trees in linux-next as there seems to be
no other way to stop this?
On Wed, Jul 15, 2026 at 09:55:01PM +0800, kernel test robot wrote:
>
> hi, Tetsuo Handa,
>
> this report is just FYI.
> we understand d908729e74 is an experimental patch, and it seems there are lots
> of print while running stress-ng.umount tests (one dmesg is attached)
>
> [ 59.370110][T10457] do_umount: task=stress-ng-umoun[10457] propagate_mount_busy()!=0
> [ 59.394831][T10476] do_umount: task=stress-ng-umoun[10476] propagate_mount_busy()!=0
> [ 59.404989][T10477] do_umount: task=stress-ng-umoun[10477] propagate_mount_busy()!=0
> [ 59.414578][T10473] do_umount: task=stress-ng-umoun[10473] propagate_mount_busy()!=0
> [ 59.423911][T10460] do_umount: task=stress-ng-umoun[10460] propagate_mount_busy()!=0
>
> ....
>
>
> so the very slow performance is expected?
>
> just FYI what we observed in our tests.
>
>
>
> Hello,
>
> kernel test robot noticed a 100.0% regression of stress-ng.umount.ops_per_sec on:
>
>
> commit: d908729e7467462bce1db3bc1bffec2e2d1f6c81 ("loop: Fix NULL pointer dereference in lo_rw_aio()")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [still regression on linux-next/master bee763d5f341b99cf472afeb508d4988f62a6ca1]
>
> testcase: stress-ng
> config: x86_64-rhel-9.4
> compiler: gcc-14
> test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 512G memory
> parameters:
>
> nr_threads: 100%
> testtime: 60s
> test: umount
> cpufreq_governor: performance
>
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202607151655.9d74999d-lkp@intel.com
>
>
> Details are as below:
> -------------------------------------------------------------------------------------------------->
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20260715/202607151655.9d74999d-lkp@intel.com
>
> =========================================================================================
> compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
> gcc-14/performance/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-spr-2sp4/umount/stress-ng/60s
>
> commit:
> c84e50ccc1 ("net: add "struct dst_entry" debugging")
> d908729e74 ("loop: Fix NULL pointer dereference in lo_rw_aio()")
>
> c84e50ccc177911c d908729e7467462bce1db3bc1bf
> ---------------- ---------------------------
> %stddev %change %stddev
> \ | \
> 60.09 +312.8% 248.06 ± 5% stress-ng.time.elapsed_time
> 60.09 +312.8% 248.06 ± 5% stress-ng.time.elapsed_time.max
> 52760 ± 2% -81.8% 9620 ± 7% stress-ng.time.involuntary_context_switches
> 149488 ± 2% +61.8% 241879 stress-ng.time.minor_page_faults
> 2821 -53.9% 1300 ± 4% stress-ng.time.percent_of_cpu_this_job_got
> 1677 +92.6% 3230 ± 8% stress-ng.time.system_time
> 17.97 -97.9% 0.37 ± 11% stress-ng.time.user_time
> 77874729 -99.8% 190900 ± 11% stress-ng.time.voluntary_context_switches
> 804634 -99.9% 470.83 ± 10% stress-ng.umount.ops
> 13417 -100.0% 2.76 ± 11% stress-ng.umount.ops_per_sec
> 1.203e+10 ± 4% +327.1% 5.137e+10 ± 4% cpuidle..time
> 94349745 -95.2% 4565944 ± 2% cpuidle..usage
> 1703024 ± 34% -76.9% 392929 ± 20% numa-numastat.node0.local_node
> 1773100 ± 31% -73.7% 466314 ± 18% numa-numastat.node0.numa_hit
> 123.98 +151.7% 312.11 ± 3% uptime.boot
> 25137 +155.4% 64209 ± 2% uptime.idle
> 6352999 ± 29% -74.7% 1607659 ±106% numa-meminfo.node0.FilePages
> 704881 ± 39% -94.1% 41446 ± 99% numa-meminfo.node0.Mapped
> 8518453 ± 23% -61.7% 3261125 ± 55% numa-meminfo.node0.MemUsed
> 1588258 ± 29% -74.7% 401984 ±106% numa-vmstat.node0.nr_file_pages
> 176266 ± 39% -94.1% 10389 ± 99% numa-vmstat.node0.nr_mapped
> 1773189 ± 31% -73.7% 466366 ± 18% numa-vmstat.node0.numa_hit
> 1703113 ± 34% -76.9% 392981 ± 20% numa-vmstat.node0.numa_local
> 185.00 ± 5% -95.4% 8.50 ± 27% perf-c2c.DRAM.local
> 5701 ± 2% -98.1% 107.83 ± 21% perf-c2c.DRAM.remote
> 7783 ± 2% -98.6% 112.50 ± 11% perf-c2c.HITM.local
> 3903 ± 2% -98.2% 71.50 ± 23% perf-c2c.HITM.remote
> 11686 ± 2% -98.4% 184.00 ± 7% perf-c2c.HITM.total
> 86.78 +5.7% 91.72 vmstat.cpu.id
> 8536351 ± 3% -48.1% 4429833 vmstat.memory.cache
> 33.29 ± 13% -39.3% 20.20 ± 2% vmstat.procs.r
> 2684019 ± 3% -99.8% 6591 ± 3% vmstat.system.cs
> 1442389 ± 3% -97.2% 41079 ± 2% vmstat.system.in
> 86.39 +5.2 91.64 mpstat.cpu.all.idle%
> 0.72 ± 3% -0.7 0.04 ± 5% mpstat.cpu.all.irq%
> 0.23 ± 4% -0.2 0.02 ± 3% mpstat.cpu.all.soft%
> 11.97 ± 3% -3.7 8.25 ± 2% mpstat.cpu.all.sys%
> 0.70 ± 3% -0.6 0.06 ± 6% mpstat.cpu.all.usr%
> 12.17 ± 20% -83.6% 2.00 mpstat.max_utilization.seconds
> 49.16 ± 2% +33.8% 65.80 ± 9% mpstat.max_utilization_pct
> 2823884 ± 3% -99.8% 6491 ± 2% perf-stat.i.context-switches
> 84670 ± 4% -99.6% 307.43 ± 2% perf-stat.i.cpu-migrations
> 0.22 ±129% +706.3% 1.80 ± 10% perf-stat.i.major-faults
> 9097 ± 4% -60.6% 3586 ± 4% perf-stat.i.minor-faults
> 9097 ± 4% -60.6% 3587 ± 4% perf-stat.i.page-faults
> 2775019 ± 3% -99.8% 6370 ± 2% perf-stat.ps.context-switches
> 220452 +1.2% 223093 perf-stat.ps.cpu-clock
> 83771 ± 4% -99.7% 289.14 ± 2% perf-stat.ps.cpu-migrations
> 0.22 ±129% +641.0% 1.63 ± 9% perf-stat.ps.major-faults
> 8892 ± 4% -65.0% 3116 ± 3% perf-stat.ps.minor-faults
> 8892 ± 4% -64.9% 3118 ± 3% perf-stat.ps.page-faults
> 220452 +1.2% 223093 perf-stat.ps.task-clock
> 4979826 ± 5% -82.7% 859490 meminfo.Active
> 4979826 ± 5% -82.7% 859490 meminfo.Active(anon)
> 67874 ± 3% +218.5% 216208 ± 4% meminfo.AnonHugePages
> 773451 -8.5% 707773 meminfo.AnonPages
> 8352548 ± 3% -48.8% 4276142 meminfo.Cached
> 11362980 ± 2% -56.4% 4957049 meminfo.Committed_AS
> 161454 -6.7% 150606 meminfo.KReclaimable
> 54472 -9.1% 49515 meminfo.KernelStack
> 869412 ± 6% -87.2% 111056 meminfo.Mapped
> 12558346 ± 2% -39.8% 7562575 meminfo.Memused
> 96084 ± 4% -36.3% 61182 meminfo.PageTables
> 123466 -5.4% 116846 meminfo.Percpu
> 161454 -6.7% 150606 meminfo.SReclaimable
> 4211290 ± 6% -96.3% 155777 ± 6% meminfo.Shmem
> 12813481 ± 2% -30.9% 8854911 meminfo.max_used_kB
> 493.83 ± 3% -34.1% 325.67 ± 2% turbostat.Avg_MHz
> 17.34 ± 3% -8.6 8.76 ± 2% turbostat.Busy%
> 2847 +30.5% 3716 turbostat.Bzy_MHz
> 0.73 ± 3% -0.7 0.00 turbostat.C1%
> 63.69 ± 3% -61.1 2.60 ± 3% turbostat.C1E%
> 19.01 ± 15% +69.6 88.65 turbostat.C6%
> 66.25 ± 3% -78.0% 14.56 turbostat.CPU%c1
> 4.74 ± 69% +1352.9% 68.84 turbostat.CPU%c6
> 57.83 -12.1% 50.83 ± 2% turbostat.CoreTmp
> 0.40 -54.4% 0.18 ± 2% turbostat.IPC
> 94123962 -89.4% 9950194 ± 4% turbostat.IRQ
> 1479952 -46.5% 792469 ± 2% turbostat.NMI
> 0.50 ± 4% -0.5 0.00 turbostat.POLL%
> 1.34 ± 92% -88.7% 0.15 ± 70% turbostat.Pkg%pc2
> 58.33 -12.0% 51.33 turbostat.PkgTmp
> 444.18 -6.5% 415.23 turbostat.PkgWatt
> 24.82 -3.2% 24.01 turbostat.RAMWatt
> 2500 -39.3% 1516 ± 2% turbostat.UncMHz
> 1245044 ± 5% -82.7% 215013 proc-vmstat.nr_active_anon
> 193369 -8.5% 176889 proc-vmstat.nr_anon_pages
> 33.14 ± 3% +221.0% 106.39 ± 4% proc-vmstat.nr_anon_transparent_hugepages
> 12797945 +1.0% 12922865 proc-vmstat.nr_dirty_background_threshold
> 25627182 +1.0% 25877327 proc-vmstat.nr_dirty_threshold
> 2088218 ± 3% -48.8% 1069227 proc-vmstat.nr_file_pages
> 54471 -9.2% 49470 proc-vmstat.nr_kernel_stack
> 217415 ± 6% -87.3% 27713 ± 2% proc-vmstat.nr_mapped
> 24021 ± 4% -36.6% 15219 ± 2% proc-vmstat.nr_page_table_pages
> 1052903 ± 6% -96.3% 39135 ± 6% proc-vmstat.nr_shmem
> 40363 -6.7% 37664 proc-vmstat.nr_slab_reclaimable
> 117592 -1.9% 115335 proc-vmstat.nr_slab_unreclaimable
> 76848 -1.4% 75760 proc-vmstat.nr_vmalloc
> 1245044 ± 5% -82.7% 215013 proc-vmstat.nr_zone_active_anon
> 64270 ± 35% -69.1% 19860 ± 76% proc-vmstat.numa_hint_faults
> 43950 ± 48% -73.5% 11651 ± 54% proc-vmstat.numa_hint_faults_local
> 2412834 ± 3% -56.1% 1059866 proc-vmstat.numa_hit
> 2176941 ± 4% -62.0% 826445 proc-vmstat.numa_local
> 129575 ± 26% -71.0% 37602 ± 94% proc-vmstat.numa_pte_updates
> 2488714 ± 3% -51.6% 1204079 proc-vmstat.pgalloc_normal
> 750242 ± 3% +20.9% 906839 ± 2% proc-vmstat.pgfault
> 664570 ± 2% +68.4% 1118975 proc-vmstat.pgfree
> 36925 ± 5% +16.8% 43128 ± 6% proc-vmstat.pgreuse
> 825.17 +1301.6% 11565 ± 5% proc-vmstat.unevictable_pgs_culled
> 7006 ± 2% +325.6% 29822 ± 7% sched_debug.cfs_rq:/.avg_vruntime.avg
> 40462 ± 10% +737.4% 338834 ± 21% sched_debug.cfs_rq:/.avg_vruntime.max
> 3981 ± 3% +28.2% 5102 ± 10% sched_debug.cfs_rq:/.avg_vruntime.min
> 5154 ± 7% +782.7% 45498 ± 10% sched_debug.cfs_rq:/.avg_vruntime.stddev
> 710829 ± 34% +49.1% 1059534 ± 11% sched_debug.cfs_rq:/.load.max
> 150111 ± 10% +37.8% 206893 ± 6% sched_debug.cfs_rq:/.load.stddev
> 2208 ± 27% -64.7% 779.66 ± 41% sched_debug.cfs_rq:/.load_avg.avg
> 40413 ± 8% -57.6% 17125 ± 10% sched_debug.cfs_rq:/.load_avg.max
> 5.08 ± 26% -100.0% 0.00 sched_debug.cfs_rq:/.load_avg.min
> 7737 ± 16% -63.3% 2839 ± 22% sched_debug.cfs_rq:/.load_avg.stddev
> 76.72 ±118% -94.9% 3.87 ± 36% sched_debug.cfs_rq:/.removed.load_avg.avg
> 15144 ±136% -98.5% 221.87 ± 10% sched_debug.cfs_rq:/.removed.load_avg.max
> 1038 ±130% -97.3% 28.42 ± 17% sched_debug.cfs_rq:/.removed.load_avg.stddev
> 249.83 ± 17% -55.0% 112.31 ± 10% sched_debug.cfs_rq:/.removed.runnable_avg.max
> 249.75 ± 17% -55.0% 112.31 ± 10% sched_debug.cfs_rq:/.removed.util_avg.max
> 1081 ± 6% +14.2% 1234 ± 7% sched_debug.cfs_rq:/.runnable_avg.max
> 5.00 ± 25% -100.0% 0.00 sched_debug.cfs_rq:/.runnable_avg.min
> 162.44 ± 4% +46.5% 238.00 ± 5% sched_debug.cfs_rq:/.runnable_avg.stddev
> 108.77 ± 2% -10.9% 96.96 ± 7% sched_debug.cfs_rq:/.util_avg.avg
> 4.92 ± 25% -100.0% 0.00 sched_debug.cfs_rq:/.util_avg.min
> 162.14 ± 4% +41.0% 228.54 ± 4% sched_debug.cfs_rq:/.util_avg.stddev
> 10.43 ± 21% +218.8% 33.23 ± 27% sched_debug.cfs_rq:/.util_est.avg
> 80.66 ± 7% +87.0% 150.81 ± 10% sched_debug.cfs_rq:/.util_est.stddev
> 7006 ± 2% +325.6% 29822 ± 7% sched_debug.cfs_rq:/.zero_vruntime.avg
> 40462 ± 10% +737.4% 338834 ± 21% sched_debug.cfs_rq:/.zero_vruntime.max
> 3981 ± 3% +28.2% 5102 ± 10% sched_debug.cfs_rq:/.zero_vruntime.min
> 5154 ± 7% +782.7% 45498 ± 10% sched_debug.cfs_rq:/.zero_vruntime.stddev
> 624650 ± 2% +53.9% 961556 sched_debug.cpu.avg_idle.avg
> 22687 ± 24% +662.8% 173061 ± 8% sched_debug.cpu.avg_idle.min
> 251512 ± 3% -54.5% 114548 ± 8% sched_debug.cpu.avg_idle.stddev
> 91182 ± 2% +89.7% 172996 ± 7% sched_debug.cpu.clock.avg
> 91204 ± 2% +89.7% 173016 ± 7% sched_debug.cpu.clock.max
> 91159 ± 2% +89.7% 172961 ± 7% sched_debug.cpu.clock.min
> 90721 ± 2% +90.4% 172755 ± 7% sched_debug.cpu.clock_task.avg
> 90895 ± 2% +90.3% 172941 ± 7% sched_debug.cpu.clock_task.max
> 76103 ± 2% +104.2% 155431 ± 7% sched_debug.cpu.clock_task.min
> 989.42 +18.4% 1171 ± 2% sched_debug.cpu.clock_task.stddev
> 10278 +18.0% 12129 ± 2% sched_debug.cpu.curr->pid.max
> 1.17 ± 20% +45.7% 1.70 ± 14% sched_debug.cpu.nr_running.max
> 385890 -98.9% 4198 ± 10% sched_debug.cpu.nr_switches.avg
> 443274 -89.4% 47022 ± 29% sched_debug.cpu.nr_switches.max
> 235117 ± 13% -99.5% 1244 ± 6% sched_debug.cpu.nr_switches.min
> 26366 ± 9% -79.6% 5375 ± 19% sched_debug.cpu.nr_switches.stddev
> 117.33 ± 11% -26.5% 86.22 ± 24% sched_debug.cpu.nr_uninterruptible.max
> -112.67 -85.1% -16.74 sched_debug.cpu.nr_uninterruptible.min
> 39.13 ± 2% -77.0% 8.99 ± 17% sched_debug.cpu.nr_uninterruptible.stddev
> 91161 ± 2% +89.7% 172977 ± 7% sched_debug.cpu_clk
> 0.01 ±149% +393.8% 0.03 ± 62% sched_debug.dl_rq:.dl_nr_running.avg
> 0.03 ±117% +248.3% 0.12 ± 34% sched_debug.dl_rq:.dl_nr_running.stddev
> 90093 ± 2% +90.8% 171916 ± 7% sched_debug.ktime
> 93416 ± 2% +87.6% 175231 ± 7% sched_debug.sched_clk
> 0.02 ± 54% +4401.9% 0.79 ±106% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.anon_pipe_read.fifo_pipe_read.vfs_read.ksys_read
> 0.01 ± 9% +4e+05% 30.47 ±141% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.anon_pipe_read.vfs_read.ksys_read.do_syscall_64
> 0.11 ± 7% +254.0% 0.38 ± 66% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.devkmsg_read.vfs_read.ksys_read.do_syscall_64
> 0.01 ± 16% +1511.8% 0.09 ± 81% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.do_nanosleep.hrtimer_nanosleep.common_nsleep.__x64_sys_clock_nanosleep
> 0.03 ± 23% -98.7% 0.00 ±223% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 0.09 ±164% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsopen
> 0.02 ± 48% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 0.30 ±203% +56061.3% 165.77 ±150% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.sched_setaffinity
> 0.02 ± 26% -97.4% 0.00 ±223% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 0.98 ± 39% -97.8% 0.02 ± 39% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 0.02 ± 79% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.clock_nanosleep.[unknown]
> 0.02 ± 59% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.shim_nanosleep_uint64.[unknown]
> 0.02 ± 13% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_mwc1
> 0.01 ± 23% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 0.03 ± 82% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umount
> 0.02 ± 35% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umounter
> 0.04 ±112% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount
> 0.04 ± 85% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 0.03 ±104% -97.1% 0.00 ±223% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.[unknown]
> 0.00 ± 30% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.umount2
> 0.01 ± 43% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 0.05 ±109% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 0.00 ±101% +11082.1% 0.52 ± 94% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.path_init
> 0.04 ±114% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 0.01 ±107% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 0.44 ± 14% -82.3% 0.08 ± 96% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.__sync_rcu_exp_select_node_cpus.kthread_worker_fn.kthread
> 0.15 ± 69% -99.6% 0.00 ±141% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 1.31 ±222% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__unlock_mount.do_move_mount
> 0.01 ± 37% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 0.10 ±198% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.clone_mnt.copy_tree
> 0.11 ± 48% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 0.02 ± 72% +231.7% 0.06 ± 14% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_umount.path_umount
> 0.04 ±181% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 0.10 ± 48% -80.2% 0.02 ±193% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 0.12 ± 76% -99.0% 0.00 ±223% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 0.14 ±110% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 0.02 ±102% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.set_root.nd_jump_root
> 0.29 ±174% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 0.02 ±149% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 0.08 ± 21% +3073.8% 2.48 ± 10% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 0.01 ± 55% +288.0% 0.03 ± 52% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.sched_exec
> 0.01 ± 91% +67526.8% 4.62 ±137% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.d_path.perf_event_mmap_event.perf_event_mmap
> 0.09 ± 97% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 0.07 ±193% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 0.22 ±212% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.path_umount
> 0.02 ±155% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.terminate_walk
> 0.08 ± 97% -93.9% 0.00 ±223% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 0.03 ± 91% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 0.00 ±223% +76560.0% 0.64 ±163% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.complete_walk.do_open
> 0.00 ±223% +1211.1% 0.02 ± 95% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.lookup_fast.link_path_walk
> 0.00 ±223% +8280.0% 0.07 ± 18% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.pick_link.step_into_slowpath
> 0.04 ±105% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 0.03 ±125% -100.0% 0.00 perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 0.82 ± 15% -97.2% 0.02 ± 63% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.vprintk_emit.devkmsg_emit.constprop
> 0.06 ± 28% +2032.7% 1.30 ± 81% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.ep_poll.do_epoll_wait.__x64_sys_epoll_wait
> 0.02 ± 33% +311.1% 0.08 ± 98% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_umount
> 0.02 ± 53% +332.3% 0.07 ± 31% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.schedule_timeout.kcompactd.kthread.ret_from_fork
> 0.01 ± 67% +19158.2% 1.77 ±148% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.schedule_timeout.wait_for_completion_state.kernel_clone.__x64_sys_vfork
> 0.03 ± 25% +44693.6% 11.65 ± 39% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 0.01 ± 13% +944.1% 0.06 ± 93% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.wait_for_partner.fifo_open.do_dentry_open.vfs_open
> 0.23 ± 23% +12972.2% 30.35 ± 26% perf-sched.sch_delay.avg.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 0.02 ± 34% +2.3e+06% 367.57 ±141% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.anon_pipe_read.vfs_read.ksys_read.do_syscall_64
> 10.68 ± 73% +1737.5% 196.31 ± 64% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.devkmsg_read.vfs_read.ksys_read.do_syscall_64
> 11.85 ±110% -99.0% 0.12 ± 55% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.[unknown]
> 1.61 ± 36% -100.0% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 5.09 ±148% -99.5% 0.03 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsmount
> 0.50 ±149% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsopen
> 4.53 ±155% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 42.98 ± 29% -100.0% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 4.53 ± 32% -99.5% 0.02 ± 37% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 3.12 ± 23% -99.4% 0.02 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown].[unknown]
> 0.04 ±100% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.clock_nanosleep.[unknown]
> 0.33 ±150% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.shim_nanosleep_uint64.[unknown]
> 0.06 ± 34% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_mwc1
> 0.02 ± 22% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 0.30 ±173% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umount
> 0.08 ± 99% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umounter
> 0.06 ±107% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount
> 0.68 ±132% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 0.04 ±132% -97.4% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.[unknown]
> 0.01 ± 43% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.umount2
> 0.03 ± 24% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 0.57 ±131% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 0.01 ± 85% +1.5e+05% 11.24 ± 85% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.path_init
> 0.55 ±135% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 0.02 ±117% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 2.61 ± 4% -96.8% 0.08 ± 97% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.__sync_rcu_exp_select_node_cpus.kthread_worker_fn.kthread
> 7.15 ±145% -100.0% 0.00 ±141% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 3.92 ±222% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__unlock_mount.do_move_mount
> 0.04 ±105% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 0.10 ±182% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.clone_mnt.copy_tree
> 3.73 ± 89% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 0.04 ±160% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 21.08 ± 80% -99.9% 0.02 ±188% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 15.63 ± 89% -100.0% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 4.17 ±151% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 0.07 ±151% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.set_root.nd_jump_root
> 0.30 ±171% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 0.10 ±205% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 15.32 ± 17% +6951.2% 1080 ± 22% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 1.11 ± 80% -96.7% 0.04 ±136% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 0.01 ± 87% +9.6e+05% 78.61 ±133% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.d_path.perf_event_mmap_event.perf_event_mmap
> 0.91 ± 80% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 2.29 ±219% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 0.23 ±202% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.path_umount
> 0.05 ±166% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.terminate_walk
> 0.72 ± 95% -99.4% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 0.32 ± 90% -92.8% 0.02 ±173% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 0.27 ±118% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 0.00 ±223% +1.1e+06% 9.42 ±174% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.complete_walk.do_open
> 0.00 ±223% +3655.6% 0.06 ±120% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.lookup_fast.link_path_walk
> 0.00 ±223% +20840.0% 0.17 ± 21% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.pick_link.step_into_slowpath
> 0.72 ±117% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 1.04 ±188% -100.0% 0.00 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 6.34 ± 54% -98.6% 0.09 ±105% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.vprintk_emit.devkmsg_emit.constprop
> 23.09 ± 36% -99.1% 0.20 ±101% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 30.80 ± 44% -99.6% 0.12 ± 47% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_lock_mount
> 0.06 ±164% -96.3% 0.00 ±223% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.schedule_timeout.wait_for_completion.affine_move_task.__set_cpus_allowed_ptr
> 9.24 ± 30% +14386.8% 1338 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 11.70 ±104% -99.0% 0.12 ± 48% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 0.02 ± 71% +2303.7% 0.43 ±140% perf-sched.sch_delay.max.ms.perf_trace_sched_switch.wait_for_partner.fifo_open.do_dentry_open.vfs_open
> 14.59 ± 9% +9091.4% 1341 perf-sched.sch_delay.max.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 0.01 ± 21% +38669.0% 3.75 ± 25% perf-sched.total_sch_delay.average.ms
> 47.86 ± 25% +2808.4% 1392 ± 6% perf-sched.total_sch_delay.max.ms
> 1.06 ± 6% +14885.1% 159.57 ± 14% perf-sched.total_wait_and_delay.average.ms
> 6154176 ± 7% -99.8% 12170 ± 19% perf-sched.total_wait_and_delay.count.ms
> 3552 ± 15% +54.4% 5484 ± 9% perf-sched.total_wait_and_delay.max.ms
> 1.06 ± 6% +14664.8% 155.82 ± 14% perf-sched.total_wait_time.average.ms
> 3552 ± 15% +54.1% 5474 ± 9% perf-sched.total_wait_time.max.ms
> 799.54 -49.8% 401.38 ± 19% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.__x64_sys_pause.do_syscall_64.entry_SYSCALL_64_after_hwframe.[unknown]
> 0.24 ± 2% +268.1% 0.89 ± 53% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.do_nanosleep.hrtimer_nanosleep.common_nsleep.__x64_sys_clock_nanosleep
> 1.54 ± 2% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 3.74 ± 5% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsmount
> 4.49 ± 6% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 2.79 ± 5% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.umount2
> 3.38 ± 5% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 2.65 ± 36% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 5.77 ± 29% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 1.49 ± 22% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 2.17 ± 28% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 7.29 ± 68% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 12.41 ±178% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 4.64 ± 44% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 5.66 ± 12% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 3.59 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 6.54 ± 10% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 3.37 ± 14% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_umount.path_umount
> 6.28 ± 72% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 6.08 ± 4% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 5.76 ± 3% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 8.71 ± 14% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 3.22 ± 33% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 5.18 ± 23% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 3.09 ± 9% +249.9% 10.80 ± 20% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 2.87 ± 25% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 3.65 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 3.37 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 4.84 ± 13% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 2.48 ± 27% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 9.61 ± 8% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 4.11 ± 16% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 3.34 ± 11% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 1.64 ± 15% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.vprintk_emit.devkmsg_emit.constprop
> 11.23 ± 32% -81.7% 2.06 ±123% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.ep_poll.do_epoll_wait.__x64_sys_epoll_wait
> 129.53 ± 30% +338.0% 567.28 ± 4% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.poll_schedule_timeout.constprop.0
> 9.34 -99.5% 0.05 ±100% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 2.39 ± 5% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_lock_mount
> 1.83 ± 3% -63.4% 0.67 ± 49% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_umount
> 3.78 +29.1% 4.88 ± 11% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.schedule_timeout.rcu_gp_fqs_loop.rcu_gp_kthread.kthread
> 150.37 ± 16% +329.8% 646.28 ± 3% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 3.21 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 19.36 ± 4% +4532.3% 896.73 ± 6% perf-sched.wait_and_delay.avg.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 37.00 -38.7% 22.67 ± 10% perf-sched.wait_and_delay.count.perf_trace_sched_switch.anon_pipe_read.vfs_read.ksys_read.do_syscall_64
> 5439762 ± 4% -99.9% 5142 ± 36% perf-sched.wait_and_delay.count.perf_trace_sched_switch.do_nanosleep.hrtimer_nanosleep.common_nsleep.__x64_sys_clock_nanosleep
> 1769 ± 18% -99.9% 2.00 ±100% perf-sched.wait_and_delay.count.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.[unknown]
> 474.67 ± 23% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 426.50 ± 33% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsmount
> 527.00 ± 30% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 4818 ± 28% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.umount2
> 48588 ± 26% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 7.83 ± 47% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 4.00 ± 38% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 34.33 ± 25% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 249404 ± 65% -100.0% 118.00 ± 53% perf-sched.wait_and_delay.count.perf_trace_sched_switch.kthread_worker_fn.kthread.ret_from_fork.ret_from_fork_asm
> 23.67 ± 37% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 16.50 ± 29% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 7.67 ± 30% -93.5% 0.50 ±152% perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.memcpy_toio
> 14.83 ± 15% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 3.50 ± 39% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 49.50 ± 43% -98.0% 1.00 ±115% perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.__sync_rcu_exp_select_node_cpus.kthread_worker_fn.kthread
> 347.00 ± 15% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 12.00 ± 33% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 392.00 ± 19% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 61.50 ± 11% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_umount.path_umount
> 2.50 ± 50% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 2442 ± 27% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 1462 ± 34% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 199.67 ± 42% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 2.17 ± 67% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 3.50 ± 48% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 1194 ± 8% -15.6% 1008 ± 5% perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 56.33 ± 25% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 16.83 ± 25% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 47.17 ± 18% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 13.67 ± 20% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 32.50 ± 25% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 10.67 ± 64% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 20.50 ± 24% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 41.00 ± 14% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 139.83 ± 21% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.preempt_schedule_thunk.vprintk_emit.devkmsg_emit.constprop
> 491.83 ± 35% -93.2% 33.67 ±106% perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_hrtimeout_range_clock.ep_poll.do_epoll_wait.__x64_sys_epoll_wait
> 92.00 ± 25% -73.2% 24.67 ± 7% perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_hrtimeout_range_clock.poll_schedule_timeout.constprop.0
> 9630 ± 61% -100.0% 0.33 ±223% perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_preempt_disabled.__mutex_lock.constprop.0
> 118616 -99.9% 112.50 ±100% perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 38829 -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_lock_mount
> 117840 ± 8% -99.8% 261.33 ± 13% perf-sched.wait_and_delay.count.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_umount
> 14376 ± 14% -87.1% 1849 ± 6% perf-sched.wait_and_delay.count.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 17835 ± 65% -100.0% 0.00 perf-sched.wait_and_delay.count.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 59489 ± 5% -99.1% 551.67 ± 17% perf-sched.wait_and_delay.count.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 1555 ± 23% +88.4% 2930 ± 5% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.anon_pipe_read.fifo_pipe_read.vfs_read.ksys_read
> 1001 +13.2% 1133 ± 2% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.anon_pipe_read.vfs_read.ksys_read.do_syscall_64
> 13.17 ± 16% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 22.89 ± 59% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsmount
> 17.68 ± 32% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 28.45 ± 48% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.umount2
> 76.49 ± 37% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 9.55 ± 24% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 8.23 ± 14% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 10.57 ± 16% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 11.56 ± 24% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 32.87 ± 81% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 174.40 ±211% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 8.99 ± 44% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 28.65 ± 52% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 11.22 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 22.86 ± 13% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 11.92 ± 6% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_umount.path_umount
> 9.11 ± 49% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 36.19 ± 40% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 38.98 ± 61% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 20.29 ± 80% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 5.57 ± 66% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 10.36 ± 36% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 1000 +275.2% 3754 ± 38% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 12.97 ± 27% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 11.31 ± 24% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 16.26 ± 52% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 12.30 ± 20% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 10.89 ± 21% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 11.78 ± 8% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 2.24 ±223% +4440.6% 101.63 ±164% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.complete_walk.path_lookupat
> 11.45 ± 6% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 12.15 ± 17% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 12.68 ± 54% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.vprintk_emit.devkmsg_emit.constprop
> 44.52 ± 33% -99.6% 0.20 ±101% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 43.14 ± 24% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_lock_mount
> 9.93 ± 24% +641.9% 73.71 ±101% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.schedule_timeout.rcu_gp_fqs_loop.rcu_gp_kthread.kthread
> 2661 ± 13% +26.2% 3359 ± 10% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 29.37 ± 66% -100.0% 0.00 perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 3498 ± 17% +55.0% 5420 ± 11% perf-sched.wait_and_delay.max.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 799.53 -49.8% 401.36 ± 19% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.__x64_sys_pause.do_syscall_64.entry_SYSCALL_64_after_hwframe.[unknown]
> 0.24 ± 2% +238.3% 0.80 ± 62% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.do_nanosleep.hrtimer_nanosleep.common_nsleep.__x64_sys_clock_nanosleep
> 23.57 ± 46% +145.3% 57.82 ± 15% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.do_task_dead.do_exit.do_group_exit.__x64_sys_exit_group
> 0.48 ± 3% +34811.7% 168.91 ± 26% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.do_wait.kernel_wait4.do_syscall_64.entry_SYSCALL_64_after_hwframe
> 1.52 ± 2% -88.4% 0.18 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 2.64 ± 53% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsopen
> 4.47 ± 6% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 0.30 ±203% +56061.3% 165.77 ±150% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.sched_setaffinity
> 3.36 ± 5% -94.8% 0.17 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 1.67 ± 50% -98.7% 0.02 ± 39% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 1.06 ±135% -98.1% 0.02 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown].[unknown]
> 0.91 ±204% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.clock_nanosleep.[unknown]
> 0.10 ± 37% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.shim_nanosleep_uint64.[unknown]
> 0.74 ± 54% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_mwc1
> 5.76 ± 29% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 0.68 ± 81% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umount
> 0.06 ± 12% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umounter
> 0.12 ± 81% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount
> 1.45 ± 24% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 0.20 ±114% -99.6% 0.00 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.[unknown]
> 0.05 ± 30% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.umount2
> 2.16 ± 28% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 7.24 ± 69% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 3.17 ± 47% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.copy_folio_from_iter_atomic
> 12.37 ±179% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 4.63 ± 44% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 5.51 ± 12% -93.6% 0.35 ±141% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 3.52 ± 48% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__unlock_mount.do_move_mount
> 3.58 ± 17% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 6.39 ± 59% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.clone_mnt.copy_tree
> 6.43 ± 9% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 6.24 ± 72% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 8.57 ± 14% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 0.24 ±148% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.set_root.nd_jump_root
> 2.93 ± 35% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 5.16 ± 23% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 3.01 ± 9% +176.5% 8.32 ± 25% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 2.84 ± 25% -95.3% 0.13 ±111% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 0.00 ±223% +800.0% 0.01 ± 62% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.sched_exec
> 0.01 ±121% +82757.6% 4.56 ±137% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.d_path.perf_event_mmap_event.perf_event_mmap
> 3.56 ± 17% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 3.31 ± 15% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 2.77 ± 61% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.path_umount
> 0.32 ±114% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.terminate_walk
> 4.76 ± 14% -99.9% 0.00 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 2.45 ± 27% -91.1% 0.22 ±129% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 9.58 ± 8% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 0.00 ±223% +1144.4% 0.02 ±101% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.lookup_fast.link_path_walk
> 0.31 ±105% +2.3e+05% 728.74 ± 32% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy_next.lookup_fast.open_last_lookups
> 4.07 ± 17% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 3.31 ± 11% -100.0% 0.00 perf-sched.wait_time.avg.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 11.17 ± 32% -83.2% 1.88 ± 61% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.ep_poll.do_epoll_wait.__x64_sys_epoll_wait
> 129.48 ± 30% +338.0% 567.13 ± 4% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.poll_schedule_timeout.constprop.0
> 9.31 -100.0% 0.00 ±223% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 1.81 ± 3% -67.4% 0.59 ± 55% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_umount
> 29.92 ± 12% +545.3% 193.05 ± 63% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_timeout.msleep.ast_astdp_connector_helper_detect_ctx.drm_helper_probe_detect_ctx
> 3.75 +29.6% 4.86 ± 11% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_timeout.rcu_gp_fqs_loop.rcu_gp_kthread.kthread
> 0.66 ± 6% +29174.6% 193.31 ± 26% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.schedule_timeout.wait_for_completion_state.kernel_clone.__x64_sys_vfork
> 150.35 ± 16% +322.1% 634.64 ± 3% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
> 3.20 ± 17% -51.6% 1.55 ± 58% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 0.00 ± 44% +1113.3% 0.03 ±178% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.wait_for_partner.fifo_open.do_dentry_open.vfs_open
> 19.13 ± 4% +4429.8% 866.39 ± 6% perf-sched.wait_time.avg.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
> 1555 ± 23% +88.4% 2930 ± 5% perf-sched.wait_time.max.ms.perf_trace_sched_switch.anon_pipe_read.fifo_pipe_read.vfs_read.ksys_read
> 1001 +12.4% 1125 perf-sched.wait_time.max.ms.perf_trace_sched_switch.anon_pipe_read.vfs_read.ksys_read.do_syscall_64
> 3.33 ± 15% +56483.6% 1882 ± 8% perf-sched.wait_time.max.ms.perf_trace_sched_switch.do_wait.kernel_wait4.do_syscall_64.entry_SYSCALL_64_after_hwframe
> 12.85 ± 12% -98.6% 0.18 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsconfig
> 18.69 ± 31% -84.6% 2.88 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsmount
> 8.09 ± 68% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.fsopen
> 17.51 ± 32% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.exit_to_user_mode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.move_mount
> 38.20 ± 38% -99.5% 0.17 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.exp_funnel_lock.synchronize_rcu_expedited.namespace_unlock.do_umount
> 5.91 ± 17% -99.6% 0.02 ± 37% perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown]
> 176.10 ±209% -100.0% 0.02 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.[unknown].[unknown]
> 1.76 ±212% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.clock_nanosleep.[unknown]
> 1.02 ± 77% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.shim_nanosleep_uint64.[unknown]
> 6.73 ± 47% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_mwc1
> 8.22 ± 14% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_mounter.[unknown]
> 6.14 ± 78% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umount
> 0.12 ± 66% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.stress_umount_umounter
> 0.26 ±137% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount
> 10.30 ± 13% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_apic_timer_interrupt.umount2
> 0.21 ±107% -99.5% 0.00 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.[unknown]
> 0.06 ± 24% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.irqentry_exit.asm_sysvec_call_function_single.umount2
> 11.55 ± 24% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.__pi_memset
> 32.85 ± 81% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt._raw_spin_unlock_irqrestore
> 8.75 ± 48% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.copy_folio_from_iter_atomic
> 0.63 ±145% +77934.5% 494.87 ± 98% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.path_init
> 174.39 ±211% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_irq.irqentry_exit.asm_sysvec_apic_timer_interrupt.pcpu_alloc_noprof
> 8.98 ± 44% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.__mutex_lock.constprop.0
> 22.98 ± 18% -98.5% 0.35 ±141% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__do_sys_fsmount.do_syscall_64
> 7.46 ± 43% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.__unlock_mount.do_move_mount
> 11.22 ± 17% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.attach_recursive_mnt.isra
> 9.16 ± 49% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.clone_mnt.copy_tree
> 21.71 ± 8% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_lock_mount.part
> 11.91 ± 6% +908.8% 120.20 ± 86% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.do_umount.path_umount
> 9.08 ± 49% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.get_mountpoint.attach_recursive_mnt
> 23.27 ± 20% -72.3% 6.45 ±103% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.namespace_unlock
> 25.51 ± 34% -87.8% 3.12 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.mntput_no_expire_slowpath.path_umount
> 16.63 ± 58% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.prepend_path.__d_path
> 1.44 ±153% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.set_root.nd_jump_root
> 5.28 ± 72% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.sget_fc.get_tree_nodev
> 10.26 ± 37% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk._raw_spin_unlock.xa_erase.cleanup_mnt
> 1000 +252.8% 3530 ± 49% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.affine_move_task.__set_cpus_allowed_ptr.__sched_setaffinity
> 12.86 ± 28% -97.9% 0.27 ±122% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.cpu_stop_queue_work.stop_one_cpu.migrate_task_to
> 0.01 ±105% +1.1e+06% 78.73 ±133% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.d_path.perf_event_mmap_event.perf_event_mmap
> 10.97 ± 20% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_lock_mount.part
> 14.01 ± 26% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.down_write.do_umount.path_umount
> 5.92 ± 71% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.path_umount
> 0.99 ±160% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.fast_dput.dput.terminate_walk
> 12.15 ± 19% -100.0% 0.00 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.flush_tlb_mm_range.tlb_finish_mmu.change_prot_numa
> 10.89 ± 21% -97.4% 0.28 ±138% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.lookup_mnt.__traverse_mounts.step_into_slowpath
> 11.77 ± 8% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.prepend_path.__d_path.seq_path_root
> 0.00 ±223% +3655.6% 0.06 ±120% perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy.lookup_fast.link_path_walk
> 0.34 ±103% +2.9e+05% 975.89 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.try_to_unlazy_next.lookup_fast.open_last_lookups
> 11.44 ± 6% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_move_mount
> 11.49 ± 8% -100.0% 0.00 perf-sched.wait_time.max.ms.perf_trace_sched_switch.preempt_schedule_thunk.up_write.namespace_unlock.do_umount
> 1038 ± 69% -94.2% 59.89 ±125% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_hrtimeout_range_clock.ep_poll.do_epoll_wait.__x64_sys_epoll_wait
> 34.79 ± 31% -99.9% 0.04 ±214% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_read_slowpath.down_read.m_start
> 26.39 ± 15% -73.8% 6.92 ± 86% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_preempt_disabled.rwsem_down_write_slowpath.down_write.do_lock_mount
> 51.77 +546.3% 334.61 ± 73% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_timeout.msleep.ast_astdp_connector_helper_detect_ctx.drm_helper_probe_detect_ctx
> 7.70 ± 17% +738.0% 64.53 ±114% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_timeout.rcu_gp_fqs_loop.rcu_gp_kthread.kthread
> 14.52 ± 16% -53.9% 6.69 ± 61% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_timeout.synchronize_rcu_expedited_wait_once.synchronize_rcu_expedited_wait.rcu_exp_wait_wake
> 0.06 ±164% -96.3% 0.00 ±223% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_timeout.wait_for_completion.affine_move_task.__set_cpus_allowed_ptr
> 3.24 ± 25% +51835.8% 1681 ± 36% perf-sched.wait_time.max.ms.perf_trace_sched_switch.schedule_timeout.wait_for_completion_state.kernel_clone.__x64_sys_vfork
> 22.63 ± 29% -55.0% 10.18 ± 49% perf-sched.wait_time.max.ms.perf_trace_sched_switch.synchronize_rcu_expedited.namespace_unlock.do_umount.path_umount
> 3498 ± 17% +53.6% 5373 ± 12% perf-sched.wait_time.max.ms.perf_trace_sched_switch.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
>
>
>
>
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
---end quoted text---
^ permalink raw reply
* Re: Missing signoff in the arm-soc tree
From: Alexandre Belloni @ 2026-07-15 11:39 UTC (permalink / raw)
To: Mark Brown; +Cc: Arnd Bergmann, soc, linux-kernel, linux-next
In-Reply-To: <eeef7a7e-22a6-4b88-b23c-cade1b62edb2@sirena.org.uk>
On 13/07/2026 18:38:17+0100, Mark Brown wrote:
> On Mon, Jul 13, 2026 at 06:35:55PM +0100, Mark Brown wrote:
> > Commits
> >
> > 923588dd861ba ("ARM: mark mv78xx0 support as deprecated")
>
> > are missing a Signed-off-by from their committers
>
> Alexandre, you did a rebase which makes you the committer of all the
> commits you rebased - you need to add a signoff (git rebase --signoff
> might help).
Yeah, let me fix my mess.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply
* Re: Fixes tags need work in the drm-xe tree
From: Thomas Hellström @ 2026-07-15 11:24 UTC (permalink / raw)
To: Mark Brown, DRM XE List; +Cc: linux-kernel, linux-next
In-Reply-To: <aldq1bH-I9hhdc7q@sirena.org.uk>
On Wed, 2026-07-15 at 12:11 +0100, Mark Brown wrote:
> In commit
>
> 0aeed866cb938 ("drm/amd/display: Fix dangling pointer in CRTC reset
> function")
>
> Fixes tag
>
> Fixes: e7b07ceef2a6 ("drm/amd/display: Merge amdgpu_dm_crtc and
> dm_crtc_state")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
Same with this one. It's an amd commit and only appears in drm-xe-next
after a backmerge.
Thanks,
Thomas
^ permalink raw reply
* Re: Fixes tags need work in the drm-xe tree
From: Thomas Hellström @ 2026-07-15 11:22 UTC (permalink / raw)
To: Mark Brown, DRM XE List; +Cc: linux-kernel, linux-next
In-Reply-To: <aldqsddPPF4VaFCU@sirena.org.uk>
Hi, Mark.
On Wed, 2026-07-15 at 12:10 +0100, Mark Brown wrote:
> In commit
>
> 3b1f4d5e47b36 ("drm/amd/display: Fix dangling pointer in connector
> reset function")
>
> Fixes tag
>
> Fixes: e7b07ceef2a6 ("drm/amd/display: Merge amdgpu_dm_crtc and
> dm_crtc_state")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
This appears in the drm-xe tree only after a backmerge of drm-next, so
I don't think drm-xe is to blame here.
Thanks,
Thomas
^ permalink raw reply
* Fixes tags need work in the drm-xe tree
From: Mark Brown @ 2026-07-15 11:11 UTC (permalink / raw)
To: Thomas Hellström, DRM XE List; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
In commit
0aeed866cb938 ("drm/amd/display: Fix dangling pointer in CRTC reset function")
Fixes tag
Fixes: e7b07ceef2a6 ("drm/amd/display: Merge amdgpu_dm_crtc and dm_crtc_state")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Missing signoff in the realtek tree
From: Mark Brown @ 2026-07-15 11:10 UTC (permalink / raw)
To: James Tai, Yu-Chun Lin; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 128 bytes --]
Commit
18a9dade373ef ("arm64: dts: realtek: Add EL2 virtual timer interrupt")
is missing a Signed-off-by from its committer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Fixes tags need work in the drm-xe tree
From: Mark Brown @ 2026-07-15 11:10 UTC (permalink / raw)
To: Thomas Hellström, DRM XE List; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
In commit
3b1f4d5e47b36 ("drm/amd/display: Fix dangling pointer in connector reset function")
Fixes tag
Fixes: e7b07ceef2a6 ("drm/amd/display: Merge amdgpu_dm_crtc and dm_crtc_state")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Fixes tags need work in the powerpc-fixes tree
From: Mark Brown @ 2026-07-15 11:08 UTC (permalink / raw)
To: Madhavan Srinivasan, Michael Ellerman, PowerPC; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
In commit
c1c1ffa490fc3 ("powerpc/vtime: Initialize starttime at boot for native accounting")
Fixes tag
Fixes: cf9efce0ce31 ("powerpc: Account time using timebase rather than PURR")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Fixes tags need work in the amdgpu tree
From: Mark Brown @ 2026-07-15 11:08 UTC (permalink / raw)
To: Alex Deucher; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
In commit
75d3551f185b9 ("drm/amdkfd: Do not fail process debugfs setup on debugfs errors")
Fixes tag
Fixes: 325de6bf3328 ("amdkfd: expose pasid of secondary contexts by debugfs")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Missing signoff in the ntfs3 tree
From: Mark Brown @ 2026-07-15 11:08 UTC (permalink / raw)
To: Konstantin Komarov; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
Commit
f023839df8010 ("fs/ntfs3: fix out-of-bounds read of INDEX_ROOT in reparse/objid init")
is missing a Signed-off-by from its author
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: Add the Realtek SoC tree to linux-next
From: Mark Brown @ 2026-07-15 10:41 UTC (permalink / raw)
To: Yu-Chun Lin [林祐君]
Cc: linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
afaerber@suse.com, James Tai [戴志峰],
Stanley Chang[昌育德],
CY_Huang[黃鉦晏]
In-Reply-To: <555485abc39a4ad1b252b4fd7c5bf706@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Wed, Jul 15, 2026 at 06:25:14AM +0000, Yu-Chun Lin [林祐君] wrote:
> Could you please add the following to linux-next?
> - Git repository URL: https://git.kernel.org/pub/scm/linux/kernel/git/yu_chun/linux.git
> - Branch: for-next & fixes
fixes was already there, I've added for-next from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Alice Ryhl @ 2026-07-15 9:03 UTC (permalink / raw)
To: Greg KH
Cc: Mark Brown, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <2026071408-colt-vaseline-3250@gregkh>
On Tue, Jul 14, 2026 at 05:14:25PM +0200, Greg KH wrote:
> On Tue, Jul 14, 2026 at 04:06:00PM +0100, Mark Brown wrote:
> > On Tue, Jul 14, 2026 at 04:22:30PM +0200, Greg KH wrote:
> > > On Tue, Jul 14, 2026 at 03:19:41PM +0100, Mark Brown wrote:
> >
> > > > The resolution in -next today (when it's published, hopefully not too
> > > > long) should have integrated Alice's patch.
> >
> > > Cool, I'll copy that, thanks!
> >
> > Just pushed it out.
>
> Great, I've taken your resolution. Alice, if I messed anything up,
> please let me know.
The resolution looks good, thanks.
Alice
^ permalink raw reply
* Add the Realtek SoC tree to linux-next
From: Yu-Chun Lin [林祐君] @ 2026-07-15 6:25 UTC (permalink / raw)
To: broonie@kernel.org
Cc: linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
afaerber@suse.com, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
James Tai [戴志峰],
Stanley Chang[昌育德],
CY_Huang[黃鉦晏]
Hi Mark,
I am taking over as the maintainer for ARM/REALTEK ARCHITECTURE, while
Andreas Färber moves to a reviewer role.
Could you please add the following to linux-next?
- Git repository URL: https://git.kernel.org/pub/scm/linux/kernel/git/yu_chun/linux.git
- Branch: for-next & fixes
Best Regards,
Yu Chun Lin
^ permalink raw reply
* [STATUS] next/master - cc2b5f627e8ccbae1188ef2d8be3e451d7f933a5
From: KernelCI bot @ 2026-07-15 2:30 UTC (permalink / raw)
To: kernelci-results; +Cc: linux-next
Hello,
Status summary for next/master
Dashboard:
https://d.kernelci.org/c/next/master/cc2b5f627e8ccbae1188ef2d8be3e451d7f933a5/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: cc2b5f627e8ccbae1188ef2d8be3e451d7f933a5
origin: maestro
test start time: 2026-07-14 15:53:59.312000+00:00
Builds: 72 ✅ 2 ❌ 0 ⚠️
Boots: 167 ✅ 2 ❌ 0 ⚠️
Tests: 27164 ✅ 5168 ❌ 4602 ⚠️
### POSSIBLE REGRESSIONS
Hardware: bcm2711-rpi-4-b
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.kvm.shardfile-kvm
last run: https://d.kernelci.org/test/maestro:6a567dae18a4add13544dd0d
history: > ✅ > ❌ > ❌
Hardware: k3-am625-verdin-wifi-mallow
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.kvm.shardfile-kvm
last run: https://d.kernelci.org/test/maestro:6a5666fe18a4add135431d6d
history: > ✅ > ❌ > ❌
Hardware: sun50i-a64-pine64-plus
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.kvm.shardfile-kvm
last run: https://d.kernelci.org/test/maestro:6a56671518a4add135431d89
history: > ✅ > ❌ > ❌
Hardware: sc7180-trogdor-kingoftown
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_remoteproc_4080000
last run: https://d.kernelci.org/test/maestro:6a56643a18a4add13542f9ae
history: > ✅ > ❌ > ❌
### FIXED REGRESSIONS
Hardware: bcm2837-rpi-3-b-plus
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.device_error_logs
last run: https://d.kernelci.org/test/maestro:6a56693318a4add135432195
history: > ❌ > ✅ > ✅ > ✅
- kselftest.device_error_logs.devices_error_logs_test_device_error_logs_py
last run: https://d.kernelci.org/test/maestro:6a5672b018a4add135440499
history: > ❌ > ✅ > ✅ > ✅
Hardware: imx8mp-evk
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.alsa.alsa_mixer-test_write_default_wm8960audio_69
last run: https://d.kernelci.org/test/maestro:6a566a4f18a4add13543302f
history: > ❌ > ✅ > ✅ > ✅
- kselftest.alsa.alsa_mixer-test_write_default_wm8960audio_71
last run: https://d.kernelci.org/test/maestro:6a566a4f18a4add13543303d
history: > ❌ > ✅ > ✅ > ✅
### UNSTABLE TESTS
Hardware: imx8mp-evk
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.alsa.alsa_pcm-test
last run: https://d.kernelci.org/test/maestro:6a566a4e18a4add135432e37
history: > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_sound-wm8960
last run: https://d.kernelci.org/test/maestro:6a566cca18a4add13543580b
history: > ✅ > ❌ > ✅ > ✅
Hardware: mt8183-kukui-jacuzzi-juniper-sku16
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller0_14001000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add135430035
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dsi_14014000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add135430031
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add135430029
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add135430028
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add13543000c
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add13543000b
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add13543000a
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add13542ffff
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a56645b18a4add13542fffe
history: > ✅ > ❌ > ✅
This branch has 1 pre-existing build issues. See details in the dashboard.
Sent every day if there were changes in the past 24 hours.
Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
^ permalink raw reply
* Re: linux-next: manual merge of the mm-nonmm-unstable tree with the risc-v-fixes tree
From: Andrew Morton @ 2026-07-14 17:13 UTC (permalink / raw)
To: Mark Brown
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Paul Walmsley,
Vivian Wang
In-Reply-To: <alYh7S9n9qE8-Hc_@sirena.org.uk>
On Tue, 14 Jul 2026 12:47:57 +0100 Mark Brown <broonie@kernel.org> wrote:
> Today's linux-next merge of the mm-nonmm-unstable tree got a conflict in:
>
> mm/sparse-vmemmap.c
>
> between commit:
>
> 4edd70ee6a7d0 ("mm/sparse-vmemmap: flush_cache_vmap() after hotplugging vmemmap")
>
> from the risc-v-fixes tree and commit:
>
> 7605044cea4d2 ("riscv: mm: avoid spurious fault after hotplugging vmemmap")
>
> from the mm-nonmm-unstable tree. These appear to be two versions of the
> same fix, it looks like one needs to be chosen - I did the conflict
> resolution picking based on taste but left the non-conflicting bits of
> both changes.
OK, thanks. I'll remove "riscv: mm: avoid spurious fault after
hotplugging vmemmap" from mm.git.
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Greg KH @ 2026-07-14 15:14 UTC (permalink / raw)
To: Mark Brown
Cc: Alice Ryhl, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <b8939935-19dd-425f-aae0-8879fe3fa68b@sirena.org.uk>
On Tue, Jul 14, 2026 at 04:06:00PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2026 at 04:22:30PM +0200, Greg KH wrote:
> > On Tue, Jul 14, 2026 at 03:19:41PM +0100, Mark Brown wrote:
>
> > > The resolution in -next today (when it's published, hopefully not too
> > > long) should have integrated Alice's patch.
>
> > Cool, I'll copy that, thanks!
>
> Just pushed it out.
Great, I've taken your resolution. Alice, if I messed anything up,
please let me know.
thanks,
greg k-h
^ permalink raw reply
* linux-next: Tree for Jul 14
From: Mark Brown @ 2026-07-14 15:06 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
Hi all,
Changes since 20260713:
The realtek-fixes tree was added.
The mm-nonmm-unstable tree acquired a conflict with the risc-v-fixes tree.
The jc_docs tree acquired a conflict with the mm-unstable tree.
Non-merge commits (relative to Linus' tree): 5610
5578 files changed, 224849 insertions(+), 92145 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 428 trees (counting Linus' and 133 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Mark Brown @ 2026-07-14 15:06 UTC (permalink / raw)
To: Greg KH
Cc: Alice Ryhl, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <2026071423-joyride-gainfully-f851@gregkh>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Tue, Jul 14, 2026 at 04:22:30PM +0200, Greg KH wrote:
> On Tue, Jul 14, 2026 at 03:19:41PM +0100, Mark Brown wrote:
> > The resolution in -next today (when it's published, hopefully not too
> > long) should have integrated Alice's patch.
> Cool, I'll copy that, thanks!
Just pushed it out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Greg KH @ 2026-07-14 14:22 UTC (permalink / raw)
To: Mark Brown
Cc: Alice Ryhl, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <cc5e4243-d179-4224-a196-7337d1ac51f8@sirena.org.uk>
On Tue, Jul 14, 2026 at 03:19:41PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2026 at 02:55:14PM +0200, Greg KH wrote:
>
> > That's a diff between the two, can someone provide me with the diff I
> > should make now to the tree when I merge these branches together?
>
> The resolution in -next today (when it's published, hopefully not too
> long) should have integrated Alice's patch.
Cool, I'll copy that, thanks!
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Mark Brown @ 2026-07-14 14:19 UTC (permalink / raw)
To: Greg KH
Cc: Alice Ryhl, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <2026071439-magnify-submersed-b5c0@gregkh>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
On Tue, Jul 14, 2026 at 02:55:14PM +0200, Greg KH wrote:
> That's a diff between the two, can someone provide me with the diff I
> should make now to the tree when I merge these branches together?
The resolution in -next today (when it's published, hopefully not too
long) should have integrated Alice's patch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Greg KH @ 2026-07-14 12:55 UTC (permalink / raw)
To: Alice Ryhl
Cc: Mark Brown, Arnd Bergmann, Miguel Ojeda, Keshav Verma,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <alYvsW4eRWsA46YU@google.com>
On Tue, Jul 14, 2026 at 12:46:41PM +0000, Alice Ryhl wrote:
> On Mon, Jul 13, 2026 at 03:08:06PM +0100, Mark Brown wrote:
> > Hi all,
> >
> > Today's linux-next merge of the char-misc tree got conflicts in:
> >
> > drivers/android/binder/node.rs
> > drivers/android/binder/process.rs
> >
> > between commits:
> >
> > 6849cabfd30fb ("rust_binder: reject context manager self-transaction")
> > bc4a982889787 ("rust_binder: clear freeze listener on node removal")
> >
> > from the origin tree and commits:
> >
> > b9d17aa74ddd7 ("rust_binder: avoid allocating under node_refs for freeze listeners")
> > 521eae8326a18 ("rust_binder: avoid dropping NodeRef in update_ref() under lock")
> >
> > from the char-misc tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging. You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
> >
> > I am really not at all confident in this merge.
>
> Thanks for giving it a shot! I have a slightly different resolution
> since some lines added by commit bc4a98288978 ("rust_binder: clear
> freeze listener on node removal") need to be kept.
>
> Please see below for the diff between my resolution and yours.
>
> Alice
>
>
>
> $ git diff linux-next/master drivers/android/binder
> diff --git a/drivers/android/binder/process.rs b/drivers/android/binder/process.rs
> index c5f745c85a02..0555c4bd503e 100644
> --- a/drivers/android/binder/process.rs
> +++ b/drivers/android/binder/process.rs
> @@ -954,6 +954,8 @@ pub(crate) fn update_ref(
> // increment references on itself.
> let _to_free_by_handle;
> let _to_free_by_node;
> + let _to_free_freeze_listener;
> + let _to_free_freeze_listener_cleanup;
> let mut refs = self.node_refs.lock();
> if let Some(info) = refs.by_handle.get_mut(&handle) {
> if info.node_ref().update(inc, strong) {
> @@ -971,6 +973,14 @@ pub(crate) fn update_ref(
> unsafe { info.node_ref2().node.remove_node_info(info) };
>
> let id = info.node_ref().node.global_id();
> +
> + if let Some(freeze) = *info.freeze() {
> + if let Some(fl) = refs.freeze_listeners.remove(&freeze) {
> + _to_free_freeze_listener_cleanup = fl.on_process_cleanup(&self);
> + _to_free_freeze_listener = fl;
> + }
> + }
> +
> _to_free_by_handle = refs.by_handle.remove_node(&handle);
> _to_free_by_node = refs.by_node.remove_node(&id);
> refs.handle_is_present.release_id(handle as usize);
>
That's a diff between the two, can someone provide me with the diff I
should make now to the tree when I merge these branches together?
thanks,
greg k-h
^ permalink raw reply
* Re: linux-next: manual merge of the char-misc tree with the origin tree
From: Alice Ryhl @ 2026-07-14 12:46 UTC (permalink / raw)
To: Mark Brown
Cc: Greg KH, Arnd Bergmann, Greg Kroah-Hartman, Miguel Ojeda,
Keshav Verma, Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <alTxRkflyqvAaGc-@sirena.org.uk>
On Mon, Jul 13, 2026 at 03:08:06PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got conflicts in:
>
> drivers/android/binder/node.rs
> drivers/android/binder/process.rs
>
> between commits:
>
> 6849cabfd30fb ("rust_binder: reject context manager self-transaction")
> bc4a982889787 ("rust_binder: clear freeze listener on node removal")
>
> from the origin tree and commits:
>
> b9d17aa74ddd7 ("rust_binder: avoid allocating under node_refs for freeze listeners")
> 521eae8326a18 ("rust_binder: avoid dropping NodeRef in update_ref() under lock")
>
> from the char-misc tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> I am really not at all confident in this merge.
Thanks for giving it a shot! I have a slightly different resolution
since some lines added by commit bc4a98288978 ("rust_binder: clear
freeze listener on node removal") need to be kept.
Please see below for the diff between my resolution and yours.
Alice
$ git diff linux-next/master drivers/android/binder
diff --git a/drivers/android/binder/process.rs b/drivers/android/binder/process.rs
index c5f745c85a02..0555c4bd503e 100644
--- a/drivers/android/binder/process.rs
+++ b/drivers/android/binder/process.rs
@@ -954,6 +954,8 @@ pub(crate) fn update_ref(
// increment references on itself.
let _to_free_by_handle;
let _to_free_by_node;
+ let _to_free_freeze_listener;
+ let _to_free_freeze_listener_cleanup;
let mut refs = self.node_refs.lock();
if let Some(info) = refs.by_handle.get_mut(&handle) {
if info.node_ref().update(inc, strong) {
@@ -971,6 +973,14 @@ pub(crate) fn update_ref(
unsafe { info.node_ref2().node.remove_node_info(info) };
let id = info.node_ref().node.global_id();
+
+ if let Some(freeze) = *info.freeze() {
+ if let Some(fl) = refs.freeze_listeners.remove(&freeze) {
+ _to_free_freeze_listener_cleanup = fl.on_process_cleanup(&self);
+ _to_free_freeze_listener = fl;
+ }
+ }
+
_to_free_by_handle = refs.by_handle.remove_node(&handle);
_to_free_by_node = refs.by_node.remove_node(&id);
refs.handle_is_present.release_id(handle as usize);
^ permalink raw reply related
* linux-next: manual merge of the jc_docs tree with the mm-unstable tree
From: Mark Brown @ 2026-07-14 12:25 UTC (permalink / raw)
To: Jonathan Corbet
Cc: Andrew Morton, Linux Kernel Mailing List, Linux Next Mailing List,
Manuel Ebner, Stanislav Kinsburskii
[-- Attachment #1: Type: text/plain, Size: 6834 bytes --]
Hi all,
Today's linux-next merge of the jc_docs tree got a conflict in:
Documentation/mm/hmm.rst
between commit:
d68817e9c3198 ("mm/hmm: add hmm_range_fault_unlocked_timeout() for mmap lock-drop support")
from the mm-unstable tree and commit:
e834ee8e571d5 ("docs/mm: Fix braces")
from the jc_docs tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --combined Documentation/mm/hmm.rst
index 4e5a750748ae5,54c461e7a143f..0000000000000
--- a/Documentation/mm/hmm.rst
+++ b/Documentation/mm/hmm.rst
@@@ -156,57 -156,42 +156,57 @@@ During the ops->invalidate() callback t
update action to the range (mark range read only, or fully unmap, etc.). The
device must complete the update before the driver callback returns.
-When the device driver wants to populate a range of virtual addresses, it can
-use::
+When the device driver wants to populate a range of virtual addresses, the
+normal interface is::
- int hmm_range_fault(struct hmm_range *range);
+ int hmm_range_fault_unlocked_timeout(struct hmm_range *range,
+ unsigned long timeout);
It will trigger a page fault on missing or read-only entries if write access is
requested (see below). Page faults use the generic mm page fault code path just
-like a CPU page fault. The usage pattern is::
+like a CPU page fault.
+
+The caller must not hold ``mmap_read_lock`` before the call.
+``hmm_range_fault_unlocked_timeout()`` takes the mmap read lock internally and
+allows ``handle_mm_fault()`` to drop it during fault handling. This is required
+for VMAs whose fault handlers may release the mmap lock, for example regions
+managed by ``userfaultfd``.
+
+If the mmap lock is dropped or the range is invalidated, the function refreshes
+``range->notifier_seq`` and restarts the walk internally. ``-EINTR`` is returned
+if mmap lock acquisition is interrupted or a fatal signal is pending during
+retry handling.
+
+The timeout is specified in jiffies; passing ``0`` means retry indefinitely. The
+timeout exists to preserve caller policy for repeated mmu-notifier invalidation
+and is checked between retry attempts. HMM does not interrupt page fault
+handling when the timeout expires, but returns ``-EBUSY`` if the retry budget is
+exhausted before a stable range is obtained.
+
+The usage pattern is::
int driver_populate_range(...)
{
struct hmm_range range;
+ unsigned long timeout;
...
+ timeout = msecs_to_jiffies(HMM_RANGE_DEFAULT_TIMEOUT);
range.notifier = &interval_sub;
range.start = ...;
range.end = ...;
range.hmm_pfns = ...;
- if (!mmget_not_zero(interval_sub->notifier.mm))
+ if (!mmget_not_zero(interval_sub.mm))
return -EFAULT;
again:
- range.notifier_seq = mmu_interval_read_begin(&interval_sub);
- mmap_read_lock(mm);
- ret = hmm_range_fault(&range);
- if (ret) {
- mmap_read_unlock(mm);
- if (ret == -EBUSY)
- goto again;
- return ret;
- }
- mmap_read_unlock(mm);
+ ret = hmm_range_fault_unlocked_timeout(&range, timeout);
+ if (ret)
+ goto out_put;
take_lock(driver->update);
- if (mmu_interval_read_retry(&ni, range.notifier_seq)) {
+ if (mmu_interval_read_retry(&interval_sub, range.notifier_seq)) {
release_lock(driver->update);
goto again;
}
@@@ -215,11 -200,7 +215,11 @@@
* under the update lock */
release_lock(driver->update);
- return 0;
+ ret = 0;
+
+ out_put:
+ mmput(interval_sub.mm);
+ return ret;
}
The driver->update lock is the same lock that the driver takes inside its
@@@ -227,19 -208,6 +227,19 @@@ invalidate() callback. That lock must b
mmu_interval_read_retry() to avoid any race with a concurrent CPU page table
update.
+Holding the mmap lock across HMM faults
+=======================================
+
+Most callers should use ``hmm_range_fault_unlocked_timeout()``. If a driver
+really needs to hold the mmap lock across work outside HMM, it can use::
+
+ int hmm_range_fault(struct hmm_range *range);
+
+The mmap lock must be held by the caller and will remain held on return. This
+interface cannot support VMAs whose fault handlers need to drop the mmap lock.
+New callers should prefer ``hmm_range_fault_unlocked_timeout()`` unless they
+have a specific requirement to keep the mmap lock held across the call.
+
Leverage default_flags and pfn_flags_mask
=========================================
@@@ -253,8 -221,8 +253,8 @@@ permission, it sets:
range->default_flags = HMM_PFN_REQ_FAULT;
range->pfn_flags_mask = 0;
-and calls hmm_range_fault() as described above. This will fill fault all pages
-in the range with at least read permission.
+and calls the HMM range fault helper as described above. This will fault
+all pages in the range with at least read permission.
Now let's say the driver wants to do the same except for one page in the range for
which it wants to have write permission. Now driver set::
@@@ -268,9 -236,9 +268,9 @@@ address == range->start + (index_of_wri
write permission i.e., if the CPU pte does not have write permission set then HMM
will call handle_mm_fault().
-After hmm_range_fault completes the flag bits are set to the current state of
-the page tables, ie HMM_PFN_VALID | HMM_PFN_WRITE will be set if the page is
-writable.
+After the HMM range fault helper completes the flag bits are set to the
+current state of the page tables, ie HMM_PFN_VALID | HMM_PFN_WRITE will be
+set if the page is writable.
Represent and manage device memory from core kernel point of view
@@@ -348,7 -316,7 +348,7 @@@ between device driver specific code an
system memory and device private memory.
One of the first steps migrate_vma_setup() does is to invalidate other
- device's MMUs with the ``mmu_notifier_invalidate_range_start(()`` and
+ device's MMUs with the ``mmu_notifier_invalidate_range_start()`` and
``mmu_notifier_invalidate_range_end()`` calls around the page table
walks to fill in the ``args->src`` array with PFNs to be migrated.
The ``invalidate_range_start()`` callback is passed a
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox