From: Nick Piggin <npiggin@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: recursive slqb_lock
Date: Sun, 1 Mar 2009 16:07:25 +0100 [thread overview]
Message-ID: <20090301150725.GB26905@wotan.suse.de> (raw)
In-Reply-To: <20090226053450.GA31108@localhost>
On Thu, Feb 26, 2009 at 01:34:50PM +0800, Wu Fengguang wrote:
> Hi Nick,
>
> I got a lockdep warning. It looks like the slqb_lock will be taken
> twice in the call chain:
>
> s_start() => take slqb_lock
> s_show()
> gather_stats() => take slqb_lock again
Hey, thanks for this. The following patch should fix it.
--
Fix the lockdep error reported by Fengguang where down_read slqb_lock
is taken twice, with the possibility for a deadlock.
Signed-off-by: Nick Piggin <npiggin@suse.de>
---
Index: linux-2.6/mm/slqb.c
===================================================================
--- linux-2.6.orig/mm/slqb.c 2009-03-02 02:05:16.000000000 +1100
+++ linux-2.6/mm/slqb.c 2009-03-02 02:05:45.000000000 +1100
@@ -3079,7 +3079,9 @@ static void __gather_stats(void *arg)
spin_unlock(&gather->lock);
}
-static void gather_stats(struct kmem_cache *s, struct stats_gather *stats)
+/* must be called with slqb_lock held */
+static void gather_stats_locked(struct kmem_cache *s,
+ struct stats_gather *stats)
{
#ifdef CONFIG_NUMA
int node;
@@ -3089,8 +3091,6 @@ static void gather_stats(struct kmem_cac
stats->s = s;
spin_lock_init(&stats->lock);
- down_read(&slqb_lock); /* hold off hotplug */
-
on_each_cpu(__gather_stats, stats, 1);
#ifdef CONFIG_NUMA
@@ -3119,10 +3119,15 @@ static void gather_stats(struct kmem_cac
}
#endif
- up_read(&slqb_lock);
-
stats->nr_objects = stats->nr_slabs * s->objects;
}
+
+static void gather_stats(struct kmem_cache *s, struct stats_gather *stats)
+{
+ down_read(&slqb_lock); /* hold off hotplug */
+ gather_stats(s, stats);
+ up_read(&slqb_lock);
+}
#endif
/*
@@ -3175,7 +3180,7 @@ static int s_show(struct seq_file *m, vo
s = list_entry(p, struct kmem_cache, list);
- gather_stats(s, &stats);
+ gather_stats_locked(s, &stats);
seq_printf(m, "%-17s %6lu %6lu %6u %4u %4d", s->name, stats.nr_inuse,
stats.nr_objects, s->size, s->objects, (1 << s->order));
next prev parent reply other threads:[~2009-03-01 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 5:34 Wu Fengguang
2009-03-01 15:07 ` Nick Piggin [this message]
2009-03-01 17:00 ` Nick Piggin
2009-03-02 3:36 ` Wu Fengguang
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=20090301150725.GB26905@wotan.suse.de \
--to=npiggin@suse.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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®