general protection fault in timers_dead_cpu
Subsystems (6)
syzbot
syzbotHello,
syzbot found the following issue on:
HEAD commit: db2ddb871435 Linux 7.2-rc7 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14ec2149580000 kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307 dashboard link: https://syzkaller.appspot.com/bug?extid=74de56995244fe32ffe2 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ec2149580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d962c6580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-db2ddb87.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/698def9fcf7a/vmlinux-db2ddb87.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fd8b6091a563/bzImage-db2ddb87.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
smpboot: CPU 1 is now offline
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 2 UID: 0 PID: 6237 Comm: syz.2.92 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__hlist_del include/linux/list.h:1029 [inline] RIP: 0010:detach_timer kernel/time/timer.c:891 [inline] RIP: 0010:migrate_timer_list kernel/time/timer.c:2493 [inline] RIP: 0010:timers_dead_cpu+0x326/0x860 kernel/time/timer.c:2541 Code: 0f 85 0c 04 00 00 48 8d 7b 08 48 8b 2b 48 89 f8 48 c1 e8 03 42 80 3c 38 00 0f 85 df 03 00 00 48 8b 43 08 48 89 c2 48 c1 ea 03 <42> 80 3c 3a 00 0f 85 b4 03 00 00 48 89 28 48 89 04 24 48 85 ed 74 RSP: 0018:ffffc900040078c0 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffff88806a523440 RCX: ffffffff81f5d5d8 RDX: 0000000000000000 RSI: ffffffff81f5d420 RDI: ffff88806a523448 RBP: dead000000000122 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: ffff88806a5258d0 R13: ffffed100d4a4b1a R14: ffff88806a6251c0 R15: dffffc0000000000 FS: 00007f01d4dfe6c0(0000) GS:ffff8880d5fec000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f9c1ca70000 CR3: 000000003de42000 CR4: 0000000000352ef0 Call Trace: <TASK> cpuhp_invoke_callback+0x3b4/0x9a0 kernel/cpu.c:194 __cpuhp_invoke_callback_range+0x158/0x1d0 kernel/cpu.c:972 cpuhp_invoke_callback_range kernel/cpu.c:996 [inline] cpuhp_down_callbacks kernel/cpu.c:1386 [inline] _cpu_down+0x523/0x1020 kernel/cpu.c:1457 cpu_down_maps_locked kernel/cpu.c:1483 [inline] cpu_down kernel/cpu.c:1491 [inline] cpu_device_down+0x82/0xc0 kernel/cpu.c:1508 device_offline drivers/base/core.c:4279 [inline] device_offline+0x2f4/0x400 drivers/base/core.c:4263 online_store+0xd1/0x180 drivers/base/core.c:2879 dev_attr_store+0x58/0x80 drivers/base/core.c:2505 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x6ac/0x1050 fs/read_write.c:687 ksys_write+0x12a/0x250 fs/read_write.c:739 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f01d579e0d9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f01d4dfe028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f01d5a25fa0 RCX: 00007f01d579e0d9 RDX: 0000000000000002 RSI: 0000200000000180 RDI: 0000000000000003 RBP: 00007f01d5835024 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f01d5a26038 R14: 00007f01d5a25fa0 R15: 00007ffe4c5cd718 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:__hlist_del include/linux/list.h:1029 [inline] RIP: 0010:detach_timer kernel/time/timer.c:891 [inline] RIP: 0010:migrate_timer_list kernel/time/timer.c:2493 [inline] RIP: 0010:timers_dead_cpu+0x326/0x860 kernel/time/timer.c:2541 Code: 0f 85 0c 04 00 00 48 8d 7b 08 48 8b 2b 48 89 f8 48 c1 e8 03 42 80 3c 38 00 0f 85 df 03 00 00 48 8b 43 08 48 89 c2 48 c1 ea 03 <42> 80 3c 3a 00 0f 85 b4 03 00 00 48 89 28 48 89 04 24 48 85 ed 74 RSP: 0018:ffffc900040078c0 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffff88806a523440 RCX: ffffffff81f5d5d8 RDX: 0000000000000000 RSI: ffffffff81f5d420 RDI: ffff88806a523448 RBP: dead000000000122 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: ffff88806a5258d0 R13: ffffed100d4a4b1a R14: ffff88806a6251c0 R15: dffffc0000000000 FS: 00007f01d4dfe6c0(0000) GS:ffff8880d5fec000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f9c1ca70000 CR3: 000000003de42000 CR4: 0000000000352ef0 ---------------- Code disassembly (best guess): 0: 0f 85 0c 04 00 00 jne 0x412 6: 48 8d 7b 08 lea 0x8(%rbx),%rdi a: 48 8b 2b mov (%rbx),%rbp d: 48 89 f8 mov %rdi,%rax 10: 48 c1 e8 03 shr $0x3,%rax 14: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) 19: 0f 85 df 03 00 00 jne 0x3fe 1f: 48 8b 43 08 mov 0x8(%rbx),%rax 23: 48 89 c2 mov %rax,%rdx 26: 48 c1 ea 03 shr $0x3,%rdx * 2a: 42 80 3c 3a 00 cmpb $0x0,(%rdx,%r15,1) <-- trapping instruction 2f: 0f 85 b4 03 00 00 jne 0x3e9 35: 48 89 28 mov %rbp,(%rax) 38: 48 89 04 24 mov %rax,(%rsp) 3c: 48 85 ed test %rbp,%rbp 3f: 74 .byte 0x74
---
This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at [email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Thomas Gleixner
maintainerQuoted 4 lines · syzbot
HEAD commit: db2ddb871435 Linux 7.2-rc7 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14ec2149580000 kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
This has NUMA_EMU=y. Either turn it off or add '-smp 2,sockets=2' to the qemu command line. Otherwise the topology code is unhappy.
Quoted 14 lines
dashboard link: https://syzkaller.appspot.com/bug?extid=74de56995244fe32ffe2 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ec2149580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d962c6580000Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-db2ddb87.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/698def9fcf7a/vmlinux-db2ddb87.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fd8b6091a563/bzImage-db2ddb87.xzIMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by [email protected]smpboot: CPU 1 is now offline
Quoted 8 lines
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 2 UID: 0 PID: 6237 Comm: syz.2.92 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__hlist_del include/linux/list.h:1029 [inline] RIP: 0010:detach_timer kernel/time/timer.c:891 [inline] RIP: 0010:migrate_timer_list kernel/time/timer.c:2493 [inline] RIP: 0010:timers_dead_cpu+0x326/0x860 kernel/time/timer.c:2541
This happens because the reproducer does two things in parallel:
1) Hotplug CPU1
2) Toggle /sys/devices/system/machinecheck/machinecheck0/ignore_ce
#2 is not serialized against CPU hotplug so it can end up interfering with the hotplug operation:
CPU0 CPU1
hotplug
kick_ap()
wait_for_ap()
hotplug
mce_cpu_pre_down()
mce_disable_cpu();
timer_delete_sync();
// CPU is still marked onlineset_ignore_ce()
on_each_cpu(mce_enable_ce, (void *)1, 1);
IPI
timer_start()
....hotplug
timers_dead_cpu()
migrate timer to CPU0
// Migrates the MCE timer of CPU1, which is a bug in itself
...
hotplug
bringup_ap()
...
identify_secondary_cpu()
mcheck_cpu_init()
__mcheck_cpu_setup_timer()
timer_setup() <- FAILThat re-initializes the active timer, which is now queued on CPU0.
What puzzled me was that debugobjects did not catch that issue. It turned out that during some rework the debug_activate() invocation for the timer migration case got lost. So debugobjects carries the wrong state. That's easy to fix:
kernel/time/timer.c +1 -0
@@ -2492,6 +2492,7 @@ static void migrate_timer_list(struct timer_base *new_base, struct hlist_head *h timer = hlist_entry(head->first, struct timer_list, entry);detach_timer (timer, false); timer->flags = (timer->flags & ~TIMER_BASEMASK ) | cpu; +debug_timer_activate (timer);internal_add_timer (new_base, timer); } }
With that it catches the culprit as expected:
ODEBUG: init active (active state 0) object: ffff88827be234a0 object type: timer_list hint: mce_timer_fn+0x0/0x280
WARNING: lib/debugobjects.c:632 at debug_print_object+0xec/0x230, CPU#1: swapper/1/0 CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-dirty #274 PREEMPT(full) RIP: 0010:debug_print_object+0x18a/0x230 Call Trace: __debug_object_init+0x230/0x3c0 timer_init_key+0x5c/0x2e0 mcheck_cpu_init+0x3e1/0x600 identify_cpu+0x1e03/0x3660 identify_secondary_cpu+0xaa/0x160 ap_starting+0xa1/0x150 start_secondary+0x66/0x110 common_startup_64+0x13e/0x157
The knee jerk "fix" is to serialize against CPU hotplug in set_ignore_ce() and the other sysfs write functions which can result in exactly the same problem. It's not only the timer. CMCI suffers from the same issue that it can be reenabled via sysfs between the "x86/mce:online" state and going completely offline. Haven't looked further, but that seems to be a general design problem in that code.
But guarding against hotplug alone solves it only partially because with partial hotplug the same issue happens when:
1) a partial hotplug goes below the "x86/mce:online" state which disarms the timer, but stops before the CPU is marked offline
2) set_ignore_ce() or one of the other sysfs write functions reenables it
3) a subsequent hotplug operation brings the CPU completely down.
The below quick hack, which I'm not proud of, cures it. I let the MCE wizards think about the underlying design problem and let them come up with a hopefully nicer solution.
Thanks,
tglx
---
arch/x86/kernel/cpu/mce/core.c +16 -0
@@ -68,6 +68,8 @@ static DEFINE_MUTEX(mce_sysfs_mutex);#define SPINUNIT 100/* 100ns */ +static struct cpumask mce_active_cpus; + DEFINE_PER_CPU_READ_MOSTLY(unsigned int, mce_num_banks); DEFINE_PER_CPU_READ_MOSTLY(struct mce_bank[MAX_NR_BANKS], mce_banks_array);
@@ -2459,6 +2461,8 @@ static void mce_cpu_restart(void *data) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!cpumask_test_cpu (smp_processor_id (), &mce_active_cpus)) +return ;__mcheck_cpu_init_generic ();__mcheck_cpu_init_prepare_banks ();__mcheck_cpu_init_timer ();
@@ -2478,6 +2482,8 @@ static void mce_disable_cmci(void *data) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!cpumask_test_cpu (smp_processor_id (), &mce_active_cpus)) +return ;cmci_clear (); }
@@ -2485,6 +2491,8 @@ static void mce_enable_ce(void *all) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!cpumask_test_cpu (smp_processor_id (), &mce_active_cpus)) +return ;cmci_reenable ();cmci_recheck ();if (all)
@@ -2540,6 +2548,7 @@ static ssize_t set_bank(struct device *s b->ctl = new;mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)();mce_restart ();mutex_unlock (&mce_sysfs_mutex);
@@ -2557,6 +2566,7 @@ static ssize_t set_ignore_ce(struct devimutex_lock (&mce_sysfs_mutex);if (mca_cfg.ignore_ce ^ !!new) { +guard (cpus_read_lock)();if (new) {/* disable ce features */ mce_timer_delete_all ();
@@ -2584,6 +2594,7 @@ static ssize_t set_cmci_disabled(structmutex_lock (&mce_sysfs_mutex);if (mca_cfg.cmci_disabled ^ !!new) { +guard (cpus_read_lock)();if (new) {/* disable cmci */ on_each_cpu (mce_disable_cmci,NULL ,1 );
@@ -2610,6 +2621,7 @@ static ssize_t store_int_with_restart(streturn ret;mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)();mce_restart ();mutex_unlock (&mce_sysfs_mutex);
@@ -2730,6 +2742,8 @@ static void mce_disable_cpu(void)if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +cpumask_clear_cpu (smp_processor_id (), &mce_active_cpus); +if (!cpuhp_tasks_frozen)cmci_clear ();
@@ -2752,6 +2766,8 @@ static void mce_reenable_cpu(void)if (b->init)wrmsrq (mca_msr_reg (i,MCA_CTL ), b->ctl); } + +cpumask_set_cpu (smp_processor_id (), &mce_active_cpus); }static int mce_cpu_dead (unsigned int cpu)
Thomas Gleixner
maintainerQuoted 3 lines · Thomas Gleixner
The below quick hack, which I'm not proud of, cures it. I let the MCE wizards think about the underlying design problem and let them come up with a hopefully nicer solution.
After talking to Borislav briefly, I came up with less ugly one.
Thanks,
tglx
---
arch/x86/kernel/cpu/mce/core.c +39 -22
@@ -1734,8 +1734,13 @@ int memory_failure(unsigned long pfn, in*/ static unsigned long check_interval =INITIAL_CHECK_INTERVAL ; -static DEFINE_PER_CPU(unsigned long, mce_next_interval); /* in jiffies */ -static DEFINE_PER_CPU(struct timer_list, mce_timer); +struct mce_poll_state { +struct timer_list timer; +unsigned long next_interval; +bool active; +}; + +static DEFINE_PER_CPU(struct mce_poll_state, mce_poll_state);static void __start_timer (struct timer_list *t,unsigned long interval) {
@@ -1764,12 +1769,12 @@ static bool should_enable_timer(unsignedstatic void mce_timer_fn (struct timer_list *t) { -struct timer_list *cpu_t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state);unsigned long iv; -WARN_ON (cpu_t != t); +WARN_ON (&pst->timer != t); - iv =__this_cpu_read (mce_next_interval); + iv = pst->next_interval;if (mce_available (this_cpu_ptr (&cpu_info)))mc_poll_banks ();
@@ -1786,7 +1791,7 @@ static void mce_timer_fn(struct timer_liif (mce_get_storm_mode ()) {__start_timer (t,HZ ); }else if (should_enable_timer (iv)) { -__this_cpu_write (mce_next_interval, iv); + pst->next_interval = iv;__start_timer (t, iv); } }
@@ -1798,14 +1803,14 @@ static void mce_timer_fn(struct timer_li*/ void mce_timer_kick (bool storm) { -struct timer_list *t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state);mce_set_storm_mode (storm);if (storm) -__start_timer (t,HZ ); +__start_timer (&pst->timer,HZ );else -__this_cpu_write (mce_next_interval, check_interval *HZ ); + pst->next_interval = check_interval *HZ ; }/* Must not be called in IRQ context where timer_delete_sync() can deadlock */
@@ -1814,7 +1819,7 @@ static void mce_timer_delete_all(void)int cpu;for_each_online_cpu (cpu) -timer_delete_sync (&per_cpu (mce_timer, cpu)); +timer_delete_sync (&per_cpu (mce_poll_state.timer, cpu)); }static void __mcheck_cpu_mce_banks_init (void )
@@ -2070,29 +2075,29 @@ static void __mcheck_cpu_clear_vendor(st } } -static void mce_start_timer (struct timer_list *t) +static void mce_start_timer (struct mce_poll_state *pst) {unsigned long iv = check_interval *HZ ;if (should_enable_timer (iv)) { -this_cpu_write (mce_next_interval, iv); -__start_timer (t, iv); + pst->next_interval = iv; +__start_timer (&pst->timer, iv); } }static void __mcheck_cpu_setup_timer (void ) { -struct timer_list *t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state); -timer_setup (t, mce_timer_fn,TIMER_PINNED ); +timer_setup (&pst->timer, mce_timer_fn,TIMER_PINNED ); }static void __mcheck_cpu_init_timer (void ) { -struct timer_list *t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state); -timer_setup (t, mce_timer_fn,TIMER_PINNED ); -mce_start_timer (t); +timer_setup (&pst->timer, mce_timer_fn,TIMER_PINNED ); +mce_start_timer (pst); }bool filter_mce (struct mce *m)
@@ -2459,6 +2464,8 @@ static void mce_cpu_restart(void *data) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!this_cpu_read (mce_poll_state.active)) +return ;__mcheck_cpu_init_generic ();__mcheck_cpu_init_prepare_banks ();__mcheck_cpu_init_timer ();
@@ -2478,6 +2485,8 @@ static void mce_disable_cmci(void *data) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!this_cpu_read (mce_poll_state.active)) +return ;cmci_clear (); }
@@ -2485,6 +2494,8 @@ static void mce_enable_ce(void *all) {if (!mce_available (raw_cpu_ptr (&cpu_info)))return ; +if (!this_cpu_read (mce_poll_state.active)) +return ;cmci_reenable ();cmci_recheck ();if (all)
@@ -2540,6 +2551,7 @@ static ssize_t set_bank(struct device *s b->ctl = new;mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)();mce_restart ();mutex_unlock (&mce_sysfs_mutex);
@@ -2557,6 +2569,7 @@ static ssize_t set_ignore_ce(struct devimutex_lock (&mce_sysfs_mutex);if (mca_cfg.ignore_ce ^ !!new) { +guard (cpus_read_lock)();if (new) {/* disable ce features */ mce_timer_delete_all ();
@@ -2584,6 +2597,7 @@ static ssize_t set_cmci_disabled(structmutex_lock (&mce_sysfs_mutex);if (mca_cfg.cmci_disabled ^ !!new) { +guard (cpus_read_lock)();if (new) {/* disable cmci */ on_each_cpu (mce_disable_cmci,NULL ,1 );
@@ -2610,6 +2624,7 @@ static ssize_t store_int_with_restart(streturn ret;mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)();mce_restart ();mutex_unlock (&mce_sysfs_mutex);
@@ -2764,21 +2779,23 @@ static int mce_cpu_dead(unsigned int cpustatic int mce_cpu_online (unsigned int cpu) { -struct timer_list *t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state);mce_device_create (cpu);mce_threshold_create_device (cpu);mce_reenable_cpu (); -mce_start_timer (t); +mce_start_timer (pst); + pst->active = true;return 0 ; }static int mce_cpu_pre_down (unsigned int cpu) { -struct timer_list *t =this_cpu_ptr (&mce_timer); +struct mce_poll_state *pst =this_cpu_ptr (&mce_poll_state); + pst->active = false;mce_disable_cpu (); -timer_delete_sync (t); +timer_delete_sync (&pst->timer);mce_threshold_remove_device (cpu);mce_device_remove (cpu);return 0 ;
Borislav Petkov
maintainerQuoted 6 lines · Thomas Gleixner
Quoted 3 lines · Thomas Gleixner
The below quick hack, which I'm not proud of, cures it. I let the MCE wizards think about the underlying design problem and let them come up with a hopefully nicer solution.
After talking to Borislav briefly, I came up with less ugly one.
Yap, LGTM.
Lemme try to unify the whole MCE percpu gunk as we spoke.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteThomas Gleixner
maintainerPATCH 1/1 timer: Keep debugobjects state consistent in migrate_timer_list()
In reply to Thomas GleixnerWhen timers are migrated away from an offline CPU the debugobjects state gets corrupted. The timer is accounted as inactive on deletion, but the enqueue on the alive CPU lacks the activation call.
That used to work, but got broken when the trace point and the debug objects call got separated. That change missed to fixup migrate_timer_list().
Add the missing debug_timer_activate() invocation to fix it.
--- kernel/time/timer.c | 1 + 1 file changed, 1 insertion(+)
kernel/time/timer.c +1 -0
@@ -2492,6 +2492,7 @@ static void migrate_timer_list(struct ti timer = hlist_entry(head->first, struct timer_list, entry);detach_timer (timer, false); timer->flags = (timer->flags & ~TIMER_BASEMASK ) | cpu; +debug_timer_activate (timer);internal_add_timer (new_base, timer); } }
[tip: core/urgent] timer: Keep debugobjects state consistent in migrate_timer_list()
The following commit has been merged into the core/urgent branch of tip:
The following commit has been merged into the core/urgent branch of tip:
Commit-ID: c793bbfc4a0a9f5a66978fc91559e9681748dbeb Gitweb: https://git.kernel.org/tip/c793bbfc4a0a9f5a66978fc91559e9681748dbeb Author: Thomas Gleixner <[email protected]> AuthorDate: Tue, 18 Aug 2026 00:14:57 +02:00 Committer: Thomas Gleixner <[email protected]> CommitterDate: Tue, 18 Aug 2026 10:51:43 +02:00
timer: Keep debugobjects state consistent in migrate_timer_list()
When timers are migrated away from an offline CPU the debugobjects state gets corrupted. The timer is accounted as inactive on deletion, but the enqueue on the alive CPU lacks the activation call.
That used to work, but got broken when the trace point and the debug objects call got separated. That change missed to fixup migrate_timer_list().
Add the missing debug_timer_activate() invocation to fix it.
--- kernel/time/timer.c | 1 + 1 file changed, 1 insertion(+)
kernel/time/timer.c +1 -0
@@ -2492,6 +2492,7 @@ static void migrate_timer_list(struct timer_base *new_base, struct hlist_head *h timer = hlist_entry(head->first, struct timer_list, entry);detach_timer (timer, false); timer->flags = (timer->flags & ~TIMER_BASEMASK ) | cpu; +debug_timer_activate (timer);internal_add_timer (new_base, timer); } }
Borislav Petkov
maintainerQuoted 4 lines · Thomas Gleixner
timers_dead_cpu()
migrate timer to CPU0// Migrates the MCE timer of CPU1, which is a bug in itself
Stupid question: can we prevent this?
As in, this timer is not migratable, do not migrate it.
But then what do you do with a timer which is not migratable and its CPU goes offline?
Perhaps cancel it...
It won't matter in the MCE case, that's for sure.
Anyway, just some musings from reading this...
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteBorislav Petkov
maintainerQuoted 10 lines · Borislav Petkov
Quoted 4 lines · Thomas Gleixner
timers_dead_cpu()
migrate timer to CPU0// Migrates the MCE timer of CPU1, which is a bug in itselfStupid question: can we prevent this?
As in, this timer is not migratable, do not migrate it.
Quoted 8 lines
But then what do you do with a timer which is not migratable and its CPU goes offline?
Perhaps cancel it...
It won't matter in the MCE case, that's for sure.
Anyway, just some musings from reading this...
Hmm, the down path does timer_delete_sync() so I guess I'm missing an aspect here about the timer migration.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteThomas Gleixner
maintainerQuoted 10 lines · Borislav Petkov
Quoted 9 lines · Borislav Petkov
Quoted 4 lines · Thomas Gleixner
timers_dead_cpu()
migrate timer to CPU0// Migrates the MCE timer of CPU1, which is a bug in itselfStupid question: can we prevent this?
As in, this timer is not migratable, do not migrate it.
We could do that, but that's just papering over the underlying issues.
Quoted 4 lines
Quoted 4 lines
But then what do you do with a timer which is not migratable and its CPU goes offline?
Perhaps cancel it...
Yes, but that's not really well defined.
Quoted 1 line
Quoted 1 line
It won't matter in the MCE case, that's for sure.
Correct. You still have CMCI ...
Quoted 4 lines
Quoted 1 line
Anyway, just some musings from reading this...
Hmm, the down path does
timer_delete_sync()so I guess I'm missing an aspect here about the timer migration.
Care to read my first reply where I described exactly how that happens?
The timer is rearmed by that sysfs muck _after_ the down callback deleted it. And the same happens to CMCI. The down callback stops it and the sysfs muck reenables it.
Alternatively we can split the hotplug callbacks and have one in the late stage of hotplug after the point of no return, which stops the timer and CMCI. Then let the existing one only care about the device stuff which requires task context. Something like the untested below.
Thanks,
tglx
---
arch/x86/kernel/cpu/mce/core.c +25 -4
@@ -2762,23 +2762,33 @@ static int mce_cpu_dead(unsigned int cpureturn 0 ; } -static int mce_cpu_online (unsigned int cpu) +static int mce_cpu_starting (unsigned int cpu) {struct timer_list *t =this_cpu_ptr (&mce_timer); -mce_device_create (cpu); -mce_threshold_create_device (cpu);mce_reenable_cpu ();mce_start_timer (t);return 0 ; } -static int mce_cpu_pre_down (unsigned int cpu) +static int mce_cpu_dying (unsigned int cpu) {struct timer_list *t =this_cpu_ptr (&mce_timer);mce_disable_cpu ();timer_delete_sync (t); +return 0 ; +} + +static int mce_cpu_online (unsigned int cpu) +{ +mce_device_create (cpu); +mce_threshold_create_device (cpu); +return 0 ; +} + +static int mce_cpu_pre_down (unsigned int cpu) +{mce_threshold_remove_device (cpu);mce_device_remove (cpu);return 0 ;
@@ -2841,6 +2851,14 @@ static __init int mcheck_init_device(voi mce_cpu_dead);if (err) goto err_out_mem; +/* +* Invokes mce_cpu_starting() on all CPUs which are online when +* the state is installed. +*/ + err =cpuhp_setup_state (CPUHP_AP_X86_MCE_STARTING ,"x86/mce:starting" , + mce_cpu_starting, mce_cpu_dying); +if (err <0 ) + goto err_out_starting;/* * Invokes mce_cpu_online() on all CPUs which are online when
@@ -2856,6 +2874,9 @@ static __init int mcheck_init_device(voireturn 0 ; err_out_online: +cpuhp_remove_state (CPUHP_AP_X86_MCE_STARTING ); + +err_out_starting:cpuhp_remove_state (CPUHP_X86_MCE_DEAD ); err_out_mem:
include/linux/cpuhotplug.h +1 -0
@@ -186,6 +186,7 @@ enum cpuhp_state {CPUHP_AP_HRTIMERS_DYING ,CPUHP_AP_TICK_DYING ,CPUHP_AP_X86_TBOOT_DYING , +CPUHP_AP_X86_MCE_STARTING ,CPUHP_AP_ARM_CACHE_B15_RAC_DYING ,CPUHP_AP_ONLINE , CPUHP_TEARDOWN_CPU,
Thomas Gleixner
maintainerPATCH 1/1 x86/mce: Serialize sysfs controls against CPU hotplug
syzbot reported a NULL pointer dereference in the CPU hotplug code. It is caused by the lack of synchronizaton between CPU hotplug and MCE sysfs controls, which allows the sysfs controls to reenable not only the timer, but also the CMCI reporting on a CPU which is about to go out. A similar issue exists in the CPU online path where the timer can be enabled via sysfs control before the CPU runs the initialization of the timer.
Prevent this by:
1) Acquiring the mce_sysfs_mutex in the hotplug callbacks
2) Excluding CPUs which do not have MCE fully initialized from the sysfs control IPIs.
That covers both the CPU up and down situations.
--- arch/x86/kernel/cpu/mce/core.c | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-)
arch/x86/kernel/cpu/mce/core.c +13 -7
@@ -2447,6 +2447,12 @@ static struct syscore mce_syscore = {/* * mce_device: Sysfs support */ +static cpumask_var_t mce_device_initialized; + +static inline void on_each_enabled_cpu (smp_call_func_t func,void *arg) +{ +on_each_cpu_cond_mask (NULL , func, arg, true, mce_device_initialized); +}static void mce_cpu_restart (void *data) {
@@ -2462,7 +2468,7 @@ static void mce_cpu_restart(void *data)static void mce_restart (void ) {mce_timer_delete_all (); -on_each_cpu (mce_cpu_restart,NULL ,1 ); +on_each_enabled_cpu (mce_cpu_restart,NULL );mce_schedule_work (); }
@@ -2553,12 +2559,12 @@ static ssize_t set_ignore_ce(struct deviif (new) {/* disable ce features */ mce_timer_delete_all (); -on_each_cpu (mce_disable_cmci,NULL ,1 ); +on_each_enabled_cpu (mce_disable_cmci,NULL ); mca_cfg.ignore_ce = true; }else {/* enable ce features */ mca_cfg.ignore_ce = false; -on_each_cpu (mce_enable_ce, (void *)1 ,1 ); +on_each_enabled_cpu (mce_enable_ce, (void *)1 ); } }mutex_unlock (&mce_sysfs_mutex);
@@ -2579,12 +2585,12 @@ static ssize_t set_cmci_disabled(structif (mca_cfg.cmci_disabled ^ !!new) {if (new) {/* disable cmci */ -on_each_cpu (mce_disable_cmci,NULL ,1 ); +on_each_enabled_cpu (mce_disable_cmci,NULL ); mca_cfg.cmci_disabled = true; }else {/* enable cmci */ mca_cfg.cmci_disabled = false; -on_each_cpu (mce_enable_ce,NULL ,1 ); +on_each_enabled_cpu (mce_enable_ce,NULL ); } }mutex_unlock (&mce_sysfs_mutex);
@@ -2641,8 +2647,6 @@ static struct device_attribute *mce_devi NULL }; -static cpumask_var_t mce_device_initialized; -static void mce_device_release (struct device *dev) {kfree (dev);
@@ -2759,6 +2763,7 @@ static int mce_cpu_online(unsigned int c {struct timer_list *t =this_cpu_ptr (&mce_timer); +guard (mutex)(&mce_sysfs_mutex);mce_device_create (cpu);mce_threshold_create_device (cpu);mce_reenable_cpu ();
@@ -2770,6 +2775,7 @@ static int mce_cpu_pre_down(unsigned int {struct timer_list *t =this_cpu_ptr (&mce_timer); +guard (mutex)(&mce_sysfs_mutex);mce_disable_cpu ();timer_delete_sync (t);mce_threshold_remove_device (cpu);
Thomas Gleixner
maintainerPATCH v2 1/1 x86/mce: Serialize sysfs controls against CPU hotplug
On Fri, Oct 23 2026 at 11:18, Thomas Gleixner wrote:
syzbot reported a NULL pointer dereference in the CPU hotplug code. It is caused by the lack of synchronizaton between CPU hotplug and MCE sysfs controls, which allows the sysfs controls to reenable not only the timer, but also the CMCI reporting on a CPU which is about to go out. A similar issue exists in the CPU online path where the timer can be enabled via sysfs control before the CPU runs the initialization of the timer.
Prevent this by:
1) Serializing the sysfs writes against CPU hotplug.
2) Removing the redundant timer_setup() call in __mcheck_cpu_init_timer(), which can end up in initializing an active timer.
3) Splitting the hotplug callbacks into starting/dying and online/offline parts.
The starting/dying callbacks control the timer and the CMCI setup/teardown. The online/offline callbacks handle the device creation and teardown.
This ensures that the sysfs operations always see consistent CPU online state and the timer and CMCI are shut down at the time when the CPU goes offline and re-enabled when the CPU starts without interfering with the sysfs operations.
---
V2: Use the seperate hotplug state as sashiko rightfully pointed out
that taking the sysfs mutex in the hotplug callback can deadlock against the device creation/deletion.
---
arch/x86/kernel/cpu/mce/core.c +35 -14
@@ -2091,7 +2091,6 @@ static void __mcheck_cpu_init_timer(void) {struct timer_list *t =this_cpu_ptr (&mce_timer); -timer_setup (t, mce_timer_fn,TIMER_PINNED );mce_start_timer (t); }
@@ -2532,9 +2531,9 @@ static ssize_t set_bank(struct device *s, struct device_attribute *attr, b->ctl = new; -mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)(); +guard (mutex)(&mce_sysfs_mutex);mce_restart (); -mutex_unlock (&mce_sysfs_mutex);return size; }
@@ -2548,7 +2547,9 @@ static ssize_t set_ignore_ce(struct device *s,if (kstrtou64 (buf,0 , &new) <0 )return -EINVAL ; -mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)(); +guard (mutex)(&mce_sysfs_mutex); +if (mca_cfg.ignore_ce ^ !!new) {if (new) {/* disable ce features */
@@ -2561,7 +2562,6 @@ static ssize_t set_ignore_ce(struct device *s,on_each_cpu (mce_enable_ce, (void *)1 ,1 ); } } -mutex_unlock (&mce_sysfs_mutex);return size; }
@@ -2575,7 +2575,9 @@ static ssize_t set_cmci_disabled(struct device *s,if (kstrtou64 (buf,0 , &new) <0 )return -EINVAL ; -mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)(); +guard (mutex)(&mce_sysfs_mutex); +if (mca_cfg.cmci_disabled ^ !!new) {if (new) {/* disable cmci */
@@ -2587,7 +2589,6 @@ static ssize_t set_cmci_disabled(struct device *s,on_each_cpu (mce_enable_ce,NULL ,1 ); } } -mutex_unlock (&mce_sysfs_mutex);return size; }
@@ -2602,10 +2603,9 @@ static ssize_t store_int_with_restart(struct device *s,if (check_interval == old_check_interval)return ret; -mutex_lock (&mce_sysfs_mutex); +guard (cpus_read_lock)(); +guard (mutex)(&mce_sysfs_mutex);mce_restart (); -mutex_unlock (&mce_sysfs_mutex); -return ret; }
@@ -2755,23 +2755,33 @@ static int mce_cpu_dead(unsigned int cpu)return 0 ; } -static int mce_cpu_online (unsigned int cpu) +static int mce_cpu_starting (unsigned int cpu) {struct timer_list *t =this_cpu_ptr (&mce_timer); -mce_device_create (cpu); -mce_threshold_create_device (cpu);mce_reenable_cpu ();mce_start_timer (t);return 0 ; } -static int mce_cpu_pre_down (unsigned int cpu) +static int mce_cpu_dying (unsigned int cpu) {struct timer_list *t =this_cpu_ptr (&mce_timer);mce_disable_cpu ();timer_delete_sync (t); +return 0 ; +} + +static int mce_cpu_online (unsigned int cpu) +{ +mce_device_create (cpu); +mce_threshold_create_device (cpu); +return 0 ; +} + +static int mce_cpu_pre_down (unsigned int cpu) +{mce_threshold_remove_device (cpu);mce_device_remove (cpu);return 0 ;
@@ -2834,6 +2844,14 @@ static __init int mcheck_init_device(void) mce_cpu_dead);if (err) goto err_out_mem; +/* +* Invokes mce_cpu_starting() on all CPUs which are online when +* the state is installed. +*/ + err =cpuhp_setup_state (CPUHP_AP_X86_MCE_STARTING ,"x86/mce:starting" , + mce_cpu_starting, mce_cpu_dying); +if (err <0 ) + goto err_out_starting;/* * Invokes mce_cpu_online() on all CPUs which are online when
@@ -2849,6 +2867,9 @@ static __init int mcheck_init_device(void)return 0 ; err_out_online: +cpuhp_remove_state (CPUHP_AP_X86_MCE_STARTING ); + +err_out_starting:cpuhp_remove_state (CPUHP_X86_MCE_DEAD ); err_out_mem:
include/linux/cpuhotplug.h +1 -0
@@ -185,6 +185,7 @@ enum cpuhp_state {CPUHP_AP_HRTIMERS_DYING ,CPUHP_AP_TICK_DYING ,CPUHP_AP_X86_TBOOT_DYING , +CPUHP_AP_X86_MCE_STARTING ,CPUHP_AP_ARM_CACHE_B15_RAC_DYING ,CPUHP_AP_ONLINE , CPUHP_TEARDOWN_CPU,
Re: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
Quoted 29 lines · Thomas Gleixner
On Fri, Oct 23 2026 at 11:18, Thomas Gleixner wrote:
syzbot reported a NULL pointer dereference in the CPU hotplug code. It is caused by the lack of synchronizaton between CPU hotplug and MCE sysfs controls, which allows the sysfs controls to reenable not only the timer, but also the CMCI reporting on a CPU which is about to go out. A similar issue exists in the CPU online path where the timer can be enabled via sysfs control before the CPU runs the initialization of the timer.Prevent this by:
1) Serializing the sysfs writes against CPU hotplug.
2) Removing the redundant
timer_setup()call in__mcheck_cpu_init_timer(), which can end up in initializing an active timer.3) Splitting the hotplug callbacks into starting/dying and online/offline parts.
The starting/dying callbacks control the timer and the CMCI setup/teardown. The online/offline callbacks handle the device creation and teardown.
This ensures that the sysfs operations always see consistent CPU online state and the timer and CMCI are shut down at the time when the CPU goes offline and re-enabled when the CPU starts without interfering with the sysfs operations.
Quoted 4 lines
Fixes 9af43b54ab45 ("x86, mce: sysfs entries for new mce options")Reported-by [email protected]Signed-off-by Thomas Gleixner <[email protected]>
There are three others that seem to be the same issue.
Quoted 5 lines
---
V2: Use the seperate hotplug state as sashiko rightfully pointed out
that taking the sysfs mutex in the hotplug callback can deadlock against the device creation/deletion.
---
I was looking at this issue before and have some QEMU test cases.
These were able to hit the new Sashiko findings.
There are two separate ones.
1) Another deadlock.
2) PREEMPT_RT warning.
The diff below fixes both. Though I'm not sure the if the msleep() is okay.
Thanks,
Yazen
=====================
arch/x86/kernel/cpu/mce/core.c +53 -15
@@ -2512,12 +2512,36 @@ static ssize_t show_bank(struct device *s, struct device_attribute *attr,return sprintf (buf,"%llx\n" , b->ctl); } +/* +* The stores run with the kernfs active reference of their attribute held. +* CPU hotplug removes the attributes with cpu_hotplug_lock held and waits +* for that reference to drop. So never wait for cpu_hotplug_lock here. +* Restart the syscall instead, like lock_device_hotplug_sysfs(). +*/ +static int mce_sysfs_lock (void ) +{ +if (cpus_read_trylock ()) { +mutex_lock (&mce_sysfs_mutex); +return 0 ; + } +/* Avoid busy looping (5 ms of sleep should do). */ +msleep (5 ); +return restart_syscall (); +} + +static void mce_sysfs_unlock (void ) +{ +mutex_unlock (&mce_sysfs_mutex); +cpus_read_unlock (); +} +static ssize_t set_bank (struct device *s,struct device_attribute *attr,const char *buf,size_t size) {u8 bank =attr_to_bank (attr)->bank;struct mce_bank *b;u64 new; +int err;if (kstrtou64 (buf,0 , &new) <0 )return -EINVAL ;
@@ -2529,12 +2553,14 @@ static ssize_t set_bank(struct device *s, struct device_attribute *attr,if (!b->init)return -ENODEV ; - b->ctl = new; + err =mce_sysfs_lock (); +if (err) +return err; -guard (cpus_read_lock)(); -guard (mutex)(&mce_sysfs_mutex); + b->ctl = new;mce_restart (); +mce_sysfs_unlock ();return size; }
@@ -2543,12 +2569,14 @@ static ssize_t set_ignore_ce(struct device *s, const char *buf, size_t size) {u64 new; +int err;if (kstrtou64 (buf,0 , &new) <0 )return -EINVAL ; -guard (cpus_read_lock)(); -guard (mutex)(&mce_sysfs_mutex); + err =mce_sysfs_lock (); +if (err) +return err;if (mca_cfg.ignore_ce ^ !!new) {if (new) {
@@ -2563,6 +2591,7 @@ static ssize_t set_ignore_ce(struct device *s, } } +mce_sysfs_unlock ();return size; }
@@ -2571,12 +2600,14 @@ static ssize_t set_cmci_disabled(struct device *s, const char *buf, size_t size) {u64 new; +int err;if (kstrtou64 (buf,0 , &new) <0 )return -EINVAL ; -guard (cpus_read_lock)(); -guard (mutex)(&mce_sysfs_mutex); + err =mce_sysfs_lock (); +if (err) +return err;if (mca_cfg.cmci_disabled ^ !!new) {if (new) {
@@ -2590,6 +2621,7 @@ static ssize_t set_cmci_disabled(struct device *s, } } +mce_sysfs_unlock ();return size; }
@@ -2597,15 +2629,20 @@ static ssize_t store_int_with_restart(struct device *s,struct device_attribute *attr, const char *buf, size_t size) { - unsigned long old_check_interval = check_interval; -ssize_t ret =device_store_ulong (s, attr, buf, size); + unsigned long old_check_interval; +ssize_t ret; +int err; -if (check_interval == old_check_interval) -return ret; + err =mce_sysfs_lock (); +if (err) +return err; -guard (cpus_read_lock)(); -guard (mutex)(&mce_sysfs_mutex); -mce_restart (); + old_check_interval = check_interval; + ret =device_store_ulong (s, attr, buf, size); +if (check_interval != old_check_interval) +mce_restart (); + +mce_sysfs_unlock ();return ret; }
@@ -2769,7 +2806,8 @@ static int mce_cpu_dying(unsigned int cpu)struct timer_list *t =this_cpu_ptr (&mce_timer);mce_disable_cpu (); -timer_delete_sync (t); +/* Pinned to this dying CPU, so the callback can't be running. */ +timer_delete (t);return 0 ; }
Borislav Petkov
maintainerRe: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
Quoted 1 line · Yazen Ghannam
The diff below fixes both.
No, we've been trying hard to fix this shit and I already told tglx offlist, I am that >.< close from simply disabling any hotplug operations as long as someone touches those sysfs files.
There is no good reason to be toggling those continuously and f*ck around with CPU hotplug at the same time. You do those configurations and then done. Not whack them all the time.
So this code needs to be simplified - not made an even crazier and unmaintainable mess.
So, I don't know yet in detail how we are going to query the hotplug core whether operations are in progress but once we do, those sysfs helpers should simply do:
if (hotplug_operations_in_progress) return -ECOMEBACKLATER;
And that hotplug_operations_in_progress should include partial hotplug. I.e., has someone done partial hotplug? If so, error too.
And that's it.
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
Quoted 21 lines · Borislav Petkov
Quoted 1 line · Yazen Ghannam
The diff below fixes both.
No, we've been trying hard to fix this shit and I already told tglx offlist, I am that >.< close from simply disabling any hotplug operations as long as someone touches those sysfs files.
There is no good reason to be toggling those continuously and f*ck around with CPU hotplug at the same time. You do those configurations and then done. Not whack them all the time.
So this code needs to be simplified - not made an even crazier and unmaintainable mess.
So, I don't know yet in detail how we are going to query the hotplug core whether operations are in progress but once we do, those sysfs helpers should simply do:
if (hotplug_operations_in_progress) return -ECOMEBACKLATER;
Quoted 7 lines
And that
hotplug_operations_in_progressshould include partial hotplug. I.e., has someone done partial hotplug? If so, error too.And that's it.
Thx.
Right, so what if we deprecate this legacy machinecheck bus and put MCE stuff under the CPU bus? This could be like cpufreq and cpuidle.
I expect this would need a lot more changes, but the end result may be simpler.
Thanks,
Yazen
Borislav Petkov
maintainerRe: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
Quoted 5 lines · Yazen Ghannam
Right, so what if we deprecate this legacy machinecheck bus and put MCE stuff under the CPU bus? This could be like cpufreq and cpuidle.
I expect this would need a lot more changes, but the end result may be simpler.
And it would need at least a decade to whack because of user-visible ABI.
We should remember that proposal and point people to the /cpu/ hierarchy when new things need to be added there which are mce specific.
I would prefer not to add anything ABI-like though and let that stuff die because it does not belong there at all. But that was done a looong time ago and we're stuck with it.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteThomas Gleixner
maintainerRe: [PATCH V2] x86/mce: Serialize sysfs controls against CPU hotplug
In reply to Yazen GhannamQuoted 6 lines · Yazen Ghannam
On Wed, Oct 28, 2026 at 08:45:07PM +0100, Thomas Gleixner wrote:
These were able to hit the new Sashiko findings.There are two separate ones.
1) Another deadlock.
2)PREEMPT_RTwarning.
Grrr.
Quoted 2 lines
The diff below fixes both. Though I'm not sure the if the
msleep()is okay.
Not really.
I think I know how to fix it for real now that I understood the nasty interaction with kernfs, but I won't come around to look into it before Monday.