From: Zqiang <qiang1.zhang@intel.com>
To: paulmck@kernel.org, akpm@linux-foundation.org,
thunder.leizhen@huawei.com, frederic@kernel.org,
joel@joelfernandes.org
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3] mm: Make vmalloc_dump_obj() call in clean context
Date: Fri, 18 Nov 2022 08:34:41 +0800 [thread overview]
Message-ID: <20221118003441.3980437-1-qiang1.zhang@intel.com> (raw)
Currently, the mem_dump_obj() is invoked in call_rcu(), the
call_rcu() is maybe invoked in non-preemptive code segment,
for object allocated from vmalloc(), the following scenarios
may occur:
CPU 0
tasks context
spin_lock(&vmap_area_lock)
Interrupt context
call_rcu()
mem_dump_obj
vmalloc_dump_obj
spin_lock(&vmap_area_lock) <--deadlock
and for PREEMPT-RT kernel, the spinlock will convert to sleepable
lock, so the vmap_area_lock spinlock not allowed to get in non-preemptive
code segment. therefore, this commit make the vmalloc_dump_obj() call in
a clean context.
Signed-off-by: Zqiang <qiang1.zhang@intel.com>
---
v1->v2:
add IS_ENABLED(CONFIG_PREEMPT_RT) check.
v2->v3:
change commit message and add some comment.
mm/util.c | 4 +++-
mm/vmalloc.c | 25 +++++++++++++++++++++++++
2 files changed, 28 insertions(+), 1 deletion(-)
diff --git a/mm/util.c b/mm/util.c
index 12984e76767e..2b0222a728cc 100644
--- a/mm/util.c
+++ b/mm/util.c
@@ -1128,7 +1128,9 @@ void mem_dump_obj(void *object)
return;
if (virt_addr_valid(object))
- type = "non-slab/vmalloc memory";
+ type = "non-slab memory";
+ else if (is_vmalloc_addr(object))
+ type = "vmalloc memory";
else if (object == NULL)
type = "NULL pointer";
else if (object == ZERO_SIZE_PTR)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index ccaa461998f3..4351eafbe7ab 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -4034,6 +4034,31 @@ bool vmalloc_dump_obj(void *object)
struct vm_struct *vm;
void *objp = (void *)PAGE_ALIGN((unsigned long)object);
+ /* for non-vmalloc addr, return directly */
+ if (!is_vmalloc_addr(objp))
+ return false;
+
+ /**
+ * for non-Preempt-RT kernel, return directly. otherwise not
+ * only needs to determine whether it is in the interrupt context
+ * (in_interrupt())to avoid deadlock, but also to avoid acquire
+ * vmap_area_lock spinlock in disables interrupts or preempts
+ * critical sections, because the vmap_area_lock spinlock convert
+ * to sleepable lock
+ */
+ if (IS_ENABLED(CONFIG_PREEMPT_RT) && !preemptible())
+ return false;
+
+ /**
+ * get here, for Preempt-RT kernel, it means that we are in
+ * preemptible context(preemptible() is true), it also means
+ * that the in_interrupt() will return false.
+ * for non-Preempt-RT kernel, only needs to determine whether
+ * it is in the interrupt context(in_interrupt()) to avoid deadlock
+ */
+ if (in_interrupt())
+ return false;
+
vm = find_vm_area(objp);
if (!vm)
return false;
--
2.25.1
next reply other threads:[~2022-11-18 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 0:34 Zqiang [this message]
2022-11-22 23:05 ` Zhang, Qiang1
2022-11-28 7:59 ` Leizhen (ThunderTown)
2022-11-28 8:33 ` Zhang, Qiang1
2022-11-28 9:13 ` Leizhen (ThunderTown)
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=20221118003441.3980437-1-qiang1.zhang@intel.com \
--to=qiang1.zhang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=thunder.leizhen@huawei.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
all inboxes | Powered by JetHome®