From: chenzefeng <chenzefeng2@huawei.com>
To: <linux@armlinux.org.uk>, <matthias.schiffer@ew.tq-group.com>,
<tglx@linutronix.de>, <info@metux.net>,
<gregkh@linuxfoundation.org>
Cc: cj.chengjian@huawei.com, linux-kernel@vger.kernel.org,
chenzefeng2@huawei.com, nixiaoming@huawei.com,
linux-arm-kernel@lists.infradead.org, liucheng32@huawei.com
Subject: [PATCH] arm:unwind: fix incorrect backtrace with unwind_table
Date: Wed, 18 Sep 2019 11:09:34 +0800 [thread overview]
Message-ID: <1568776174-84980-1-git-send-email-chenzefeng2@huawei.com> (raw)
For arm, if the CONFIG_ARM_UNWIND is open, when insmod a module,
the init section add to the unwind_table, the code path as follow:
load_module
--->post_relocation
------->module_finalize
----------->maps[ARM_SEC_INIT].txt_sec = s
----------->unwind_table_add
Later if load_module success, the init section's memory will be
vfree, the code path as follow:
load_module
--->do_init_module
------->freeinit->module_init = mod->init_layout.base
------->schedule_work(&init_free_wq)
----------->do_free_init
--------------->vfree(freeinit->module_init)
But after the init section's had been vfree, but it's unwind_table
is not removed.
The issue as follow:
When insmod module A, the system alloc the "Addr1" for it's init
text section, and add it to the unwind_table list, after insmod
success, the "Addr1" would be vfreed.
Unfortunately, later insmod module B, the system alloc the "Addr1"
for it's text section, and add it to the unwind_table list, too.
And we dumpstack in module B, we may get a incorrect backtrace.
Signed-off-by: chenzefeng <chenzefeng2@huawei.com>
---
arch/arm/kernel/module.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/arch/arm/kernel/module.c b/arch/arm/kernel/module.c
index deef17f..438ed67 100644
--- a/arch/arm/kernel/module.c
+++ b/arch/arm/kernel/module.c
@@ -410,7 +410,20 @@ int module_finalize(const Elf32_Ehdr *hdr, const Elf_Shdr *sechdrs,
int i;
for (i = 0; i < ARM_SEC_MAX; i++)
- if (mod->arch.unwind[i])
+ if (mod->arch.unwind[i]) {
unwind_table_del(mod->arch.unwind[i]);
+ mod->arch.unwind[i] = NULL;
+ }
+#endif
+}
+
+void
+module_arch_freeing_init(struct module *mod)
+{
+#ifdef CONFIG_ARM_UNWIND
+ if (mod->arch.unwind[ARM_SEC_INIT]) {
+ unwind_table_del(mod->arch.unwind[ARM_SEC_INIT]);
+ mod->arch.unwind[ARM_SEC_INIT] = NULL;
+ }
#endif
}
--
1.8.5.6
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-09-18 3:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1568776174-84980-1-git-send-email-chenzefeng2@huawei.com \
--to=chenzefeng2@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liucheng32@huawei.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=nixiaoming@huawei.com \
--cc=tglx@linutronix.de \
/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