From: Clark Williams <williams@redhat.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Thomas Gleixner <tglx@glx-um.de>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
RT <linux-rt-users@vger.kernel.org>,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [RFC] mm: change irqs_disabled() test to spin_is_locked() in mem_cgroup_swapout
Date: Fri, 29 May 2015 10:48:15 -0500 [thread overview]
Message-ID: <20150529104815.2d2e880c@sluggy> (raw)
Johannes,
We are seeing a panic in the latest RT kernel (4.0.4-rt1) where a
VM_BUG_ON(!irqs_disabled()) in mm/memcontrol.c fires. This is because on
an RT kernel, rt_mutexes (which replace spinlocks) don't disable
interrupts while the lock is held. I talked to Steven and he suggested
that we replace the irqs_disabled() with spin_is_held().
Does this patch work for you?
Clark
From: Clark Williams <williams@redhat.com>
Date: Fri, 29 May 2015 10:28:55 -0500
Subject: [PATCH] mm: change irqs_disabled() to spin_is_locked() in mem_cgroup_swapout()
The irqs_disabled() check in mem_cgroup_swapout() fails on the latest
RT kernel because RT mutexes do not disable interrupts when held. Change
the test for the lock being held to use spin_is_locked.
Reported-by: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Clark Williams <williams@redhat.com>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 9da0f3e9c1f3..70befa14a8ce 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -5845,7 +5845,7 @@ void mem_cgroup_swapout(struct page *page,
swp_entry_t entry) page_counter_uncharge(&memcg->memory, 1);
/* XXX: caller holds IRQ-safe mapping->tree_lock */
- VM_BUG_ON(!irqs_disabled());
+ VM_BUG_ON(!spin_is_locked(&page_mapping(page)->tree_lock));
mem_cgroup_charge_statistics(memcg, page, -1);
memcg_check_events(memcg, page);
--
2.1.0
next reply other threads:[~2015-05-29 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 15:48 Clark Williams [this message]
2015-05-29 19:11 ` [RFC] mm: change irqs_disabled() test to spin_is_locked() in mem_cgroup_swapout Johannes Weiner
2015-05-29 19:21 ` Steven Rostedt
2015-05-29 21:26 ` Andrew Morton
2015-06-01 18:14 ` [RFC][PATCH] mm: ifdef out VM_BUG_ON check on PREEMPT_RT_FULL Clark Williams
2015-06-01 19:00 ` Johannes Weiner
2015-06-01 19:28 ` Steven Rostedt
2015-06-11 11:40 ` Sebastian Andrzej Siewior
2015-06-19 18:00 ` Johannes Weiner
2015-07-08 15:44 ` Sebastian Andrzej Siewior
2015-07-09 15:07 ` Thomas Gleixner
2015-07-09 16:00 ` Johannes Weiner
2015-07-09 16:43 ` Thomas Gleixner
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=20150529104815.2d2e880c@sluggy \
--to=williams@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=rostedt@goodmis.org \
--cc=tglx@glx-um.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;
as well as URLs for NNTP newsgroup(s).