Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
	namcao@linutronix.de
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 Andrew Jones <ajones@ventanamicro.com>,
	linux-riscv@lists.infradead.org,  linux-kernel@vger.kernel.org,
	andrew.jones@oss.qualcomm.com,  ganboing@gmail.com
Subject: Re: [PATCH] riscv: drop __init from vec_check_unaligned_access_speed_all_cpus
Date: Wed, 29 Jul 2026 13:23:58 -0600 (MDT)	[thread overview]
Message-ID: <20d05ee9-3c76-c9f6-6a16-755f855a1ced@kernel.org> (raw)
In-Reply-To: <20260612-vec_unaligned_drop_init-v1-1-df969210ae34@oss.tenstorrent.com>

Hi,

On Fri, 12 Jun 2026, Anirudh Srinivasan wrote:

> This function runs within a kthread and need not necessarily finish
> before system finishes boot and free_initmem() unmaps the .init.text
> section. This function makes calls to SBI for probing unaligned access
> speed, and if this is slow for some reason (say some debug prints were
> added to SBI), the kthread can still be running at this point and result
> in an instruction page fault when trying to fetch from the freed region.
> 
> [   25.642087] Unable to handle kernel paging request at virtual address ffffffff80a04ef8
> [   25.646694] Current vec_check_unali pgtable: 4K pagesize, 48-bit VAs, pgdp=0x00004000316e9000
> [   25.653170] [ffffffff80a04ef8] pgd=000010004be7e401, p4d=000010004be7e401, pud=000010004be7e001, pmd=000010000c3000e3
> [   25.661244] Oops [#1]
> [   25.662997] Modules linked in:
> [   25.665357] CPU: 3 UID: 0 PID: 42 Comm: vec_check_unali Not tainted 7.0.0-tt-blackhole-asrinivasan-00007-g30ff73f18211 #570 PREEMPTLAZY
> [   25.674669] Hardware name: Tenstorrent Blackhole (DT)
> [   25.678545] epc : vec_check_unaligned_access_speed_all_cpus+0x18/0x2c
> [   25.683458]  ra : vec_check_unaligned_access_speed_all_cpus+0x18/0x2c
> [   25.688372] epc : ffffffff80a04ef8 ra : ffffffff80a04ef8 sp : ffff8f8000203e20
> [   25.693874]  gp : ffffffff814dc168 tp : ffffaf8001ad9900 t0 : 0000000000000000
> [   25.699401]  t1 : fffffffffffffff0 t2 : ffffaf8001ad9a10 s0 : ffff8f8000203e30
> [   25.704912]  s1 : ffffaf80018dc780 a0 : 0000000000000000 a1 : 0000000000000002
> [   25.710407]  a2 : 00000000000001f0 a3 : 0000000000000018 a4 : 0000000000000000
> [   25.715917]  a5 : 0000000000000000 a6 : ffffaf8001c03d98 a7 : ffffaf8001c03e30
> [   25.721419]  s2 : ffff8f8000023c98 s3 : ffffaf8001aa1240 s4 : ffffffff80a04ee0
> [   25.726937]  s5 : 0000000000000000 s6 : 0000000000000000 s7 : 0000000000000000
> [   25.732450]  s8 : 0000000000000000 s9 : 0000000000000000 s10: 0000000000000000
> [   25.737944]  s11: 0000000000000000 t3 : 0000000000000002 t4 : 0000000000000402
> [   25.743481]  t5 : 0000000000000040 t6 : 0000000000000004 ssp : 0000000000000000
> [   25.749024] status: 0000000200000120 badaddr: ffffffff80a04ef8 cause: 000000000000000c
> [   25.755060] [<ffffffff80a04ef8>] vec_check_unaligned_access_speed_all_cpus+0x18/0x2c
> [   25.760964] [<ffffffff80047a10>] kthread+0xd8/0xfc
> [   25.764660] [<ffffffff80010c48>] ret_from_fork_kernel+0x18/0x1c4
> [   25.769220] [<ffffffff80895fe6>] ret_from_fork_kernel_asm+0x16/0x18
> [   25.774018] Code: cccc cccc cccc cccc cccc cccc cccc cccc cccc cccc (cccc) cccc
> 
> Drop __init from its signature so that this doesn't happen.

I've queued this one for v7.2-rc, since it is a narrow, targeted fix for a 
specific issue; and will plan to queue Nam's patches for v7.3.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2026-07-29 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 16:24 [PATCH] riscv: drop __init from vec_check_unaligned_access_speed_all_cpus Anirudh Srinivasan
2026-06-12 21:23 ` Nam Cao
2026-06-15 17:22   ` Anirudh Srinivasan
2026-06-16  9:23     ` Nam Cao
2026-07-29 19:23 ` Paul Walmsley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20d05ee9-3c76-c9f6-6a16-755f855a1ced@kernel.org \
    --to=pjw@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=ganboing@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox