linux-kernel - drivers/perf: riscv: BUG: using smp_processor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20240820074925.ReMKUPP3@linutronix.de>
Date: Tue, 20 Aug 2024 09:49:25 +0200
From: Nam Cao <namcao@...utronix.de>
To: Atish Patra <atishp@...osinc.com>, Palmer Dabbelt <palmer@...osinc.com>,
	Anup Patel <anup@...infault.org>,
	Conor Dooley <conor.dooley@...rochip.com>,
	Andrew Jones <ajones@...tanamicro.com>,
	Samuel Holland <samuel.holland@...ive.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: drivers/perf: riscv: BUG: using smp_processor_id() in preemptible

Hi,

I noticed the following issue on 6.11.0-rc4 with CONFIG_DEBUG_PREEMPT=y.

BUG: using smp_processor_id() in preemptible [00000000] code: swapper/0/1
caller is debug_smp_processor_id+0x1c/0x26
CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc4 #2
Hardware name: StarFive VisionFive 2 v1.3B (DT)
Call Trace:
    dump_backtrace+0x1c/0x24
    show_stack+0x2c/0x38
    dump_stack_lvl+0x5a/0x72
    dump_stack+0x14/0x1c
    check_preemption_disabled+0xb6/0xb8
    debug_smp_processor_id+0x1c/0x26
    pmu_sbi_device_probe+0x474/0x570
    platform_probe+0x52/0x96
    really_probe+0x82/0x202
    __driver_probe_device+0x5c/0xd0
    driver_probe_device+0x2c/0xb0
    __device_attach_driver+0x6e/0x8e
    bus_for_each_drv+0x64/0xb8
    __device_attach+0x82/0x144
    device_initial_probe+0xe/0x16
    bus_probe_device+0x86/0x88
    device_add+0x508/0x6ac
    platform_device_add+0xcc/0x1c8
    platform_device_register_full+0xee/0x142
    pmu_sbi_devinit+0xd4/0x11c
    do_one_initcall+0x58/0x19c
    kernel_init_freeable+0x210/0x27a
    kernel_init+0x1e/0x112
    ret_from_fork+0xe/0x1c

If you fix the issue, please add:
Reported-by: Nam Cao <namcao@...utronix.de>

Best regards,
Nam