public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Miles Lane <miles.lane@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Ben Collins <bcollins@ubuntu.com>, Greg KH <gregkh@suse.de>
Subject: [RFT PATCH 1/2] ieee1394: nodemgr: fix rwsem recursion
Date: Wed, 6 Sep 2006 19:04:38 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.a76041f4792feb5b@s5r6.in-berlin.de> (raw)
In-Reply-To: <44FEFC68.90201@s5r6.in-berlin.de>

nodemgr_update_pdrv grabbed an rw semaphore (as reader) which was
already taken by its caller's caller, nodemgr_probe_ne (as reader too).
Reported by Miles Lane, call path pointed out by Arjan van de Ven.

FIXME:
Shouldn't we rather use class->sem there, not class->subsys.rwsem?

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
Index: linux/drivers/ieee1394/nodemgr.c
===================================================================
--- linux.orig/drivers/ieee1394/nodemgr.c	2006-08-30 20:47:57.000000000 +0200
+++ linux/drivers/ieee1394/nodemgr.c	2006-09-06 19:03:24.000000000 +0200
@@ -1316,6 +1316,7 @@ static void nodemgr_node_scan(struct hos
 }
 
 
+/* Caller needs to hold nodemgr_ud_class.subsys.rwsem as reader. */
 static void nodemgr_suspend_ne(struct node_entry *ne)
 {
 	struct class_device *cdev;
@@ -1368,15 +1369,14 @@ static void nodemgr_resume_ne(struct nod
 }
 
 
+/* Caller needs to hold nodemgr_ud_class.subsys.rwsem as reader. */
 static void nodemgr_update_pdrv(struct node_entry *ne)
 {
 	struct unit_directory *ud;
 	struct hpsb_protocol_driver *pdrv;
-	struct class *class = &nodemgr_ud_class;
 	struct class_device *cdev;
 
-	down_read(&class->subsys.rwsem);
-	list_for_each_entry(cdev, &class->children, node) {
+	list_for_each_entry(cdev, &nodemgr_ud_class.children, node) {
 		ud = container_of(cdev, struct unit_directory, class_dev);
 		if (ud->ne != ne || !ud->device.driver)
 			continue;
@@ -1389,7 +1389,6 @@ static void nodemgr_update_pdrv(struct n
 			up_write(&ud->device.bus->subsys.rwsem);
 		}
 	}
-	up_read(&class->subsys.rwsem);
 }
 
 
@@ -1420,6 +1419,8 @@ static void nodemgr_irm_write_bc(struct 
 }
 
 
+/* Caller needs to hold nodemgr_ud_class.subsys.rwsem as reader because the
+ * calls to nodemgr_update_pdrv() and nodemgr_suspend_ne() here require it. */
 static void nodemgr_probe_ne(struct host_info *hi, struct node_entry *ne, int generation)
 {
 	struct device *dev;



  reply	other threads:[~2006-09-06 17:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 17:37 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected Miles Lane
2006-09-05 18:13 ` Andrew Morton
2006-09-05 18:16   ` Miles Lane
2006-09-05 19:03     ` Stefan Richter
2006-09-05 19:19       ` Miles Lane
2006-09-05 19:51         ` Stefan Richter
2006-09-05 19:23   ` Stefan Richter
2006-09-05 21:07     ` Arjan van de Ven
2006-09-05 22:27       ` Stefan Richter
2006-09-06  0:10         ` Adrian Bunk
2006-09-06  7:13     ` Stefan Richter
2006-09-06 16:50       ` Stefan Richter
2006-09-06 17:04         ` Stefan Richter [this message]
2006-09-06 17:06           ` [RFT PATCH 2/2] ieee1394: nodemgr: grab class.subsys.rwsem in nodemgr_resume_ne Stefan Richter
2006-09-07 22:45         ` 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected Miles Lane
2006-09-07 23:23           ` Stefan Richter
2006-09-06 22:35       ` Greg KH
2006-09-05 19:49   ` Miles Lane
2006-09-05 20:19     ` Stefan Richter
2006-09-05 20:26       ` Stefan Richter
2006-09-05 20:33       ` Andrew Morton
2006-09-06  6:39 ` Arjan van de Ven

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=tkrat.a76041f4792feb5b@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@osdl.org \
    --cc=bcollins@ubuntu.com \
    --cc=gregkh@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.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