Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ju Nan <junan76@163.com>
To: egg12138@foxmail.com
Cc: jpoimboe@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	linux@armlinux.org.uk, pmladek@suse.com, Ju Nan <junan76@163.com>
Subject: Re: [PATCH v3] ARM: module.lds: fix unwind metadata for merged .text sections
Date: Mon, 27 Jul 2026 15:47:09 +0800	[thread overview]
Message-ID: <20260727074708.115112-2-junan76@163.com> (raw)
In-Reply-To: <tencent_08845B64E5F38EB7FA1779982A071AB4A607@qq.com>

I ran into exactly the same on a STM32MP157A-DK1 board (dual Cortex-A7,
ARMv7 AEABI, CONFIG_ARM_UNWIND=y).  An out-of-tree module whose functions
GCC had placed in .text.unlikely (merged into .text by module.lds.S) left
its .ARM.exidx.text.unlikely section unregistered, so an Oops inside the
module produced an empty backtrace:

  Call trace:
  unwind: Index not found bf102018

With this patch applied, the module's exidx is coalesced into a single
.ARM.exidx output section, module_finalize() registers it against .text,
and the full module backtrace is restored:

  Call trace:
   do_the_crash [oops_null] from level_one+0x8/0xc [oops_null]
   level_one [oops_null] from level_two+0x8/0xc [oops_null]
   level_two [oops_null] from trigger_write+0x18/0x20 [oops_null]
   trigger_write [oops_null] from full_proxy_write+0x54/0x78
   full_proxy_write from vfs_write+0xd0/0x49c
   vfs_write from ksys_write+0x6c/0xf4
   ksys_write from ret_fast_syscall+0x0/0x54

Tested on Linux 7.1.4

Tested-by: Ju Nan <junan76@163.com>



      reply	other threads:[~2026-07-27  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 15:46 [PATCH v3] ARM: module.lds: fix unwind metadata for merged .text sections Egg12138
2026-07-27  7:47 ` Ju Nan [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=20260727074708.115112-2-junan76@163.com \
    --to=junan76@163.com \
    --cc=egg12138@foxmail.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=pmladek@suse.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