Messages in this thread |  | | Subject | Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected | From | Arjan van de Ven <> | Date | Tue, 05 Sep 2006 23:07:59 +0200 |
| |
On Tue, 2006-09-05 at 21:23 +0200, Stefan Richter wrote: > Andrew Morton wrote: > > On Tue, 5 Sep 2006 10:37:51 -0700 > > "Miles Lane" <miles.lane@gmail.com> wrote: > > > >> ieee1394: Node changed: 0-01:1023 -> 0-00:1023 > >> ieee1394: Node changed: 0-02:1023 -> 0-01:1023 > >> ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0080880002103eae] > >> > >> ============================================= > >> [ INFO: possible recursive locking detected ] > >> 2.6.18-rc5-mm1 #2 > >> --------------------------------------------- > >> knodemgrd_0/2321 is trying to acquire lock: > >> (&s->rwsem){----}, at: [<f8958897>] nodemgr_probe_ne+0x311/0x38d [ieee1394] > >> > >> but task is already holding lock: > >> (&s->rwsem){----}, at: [<f8959078>] nodemgr_host_thread+0x717/0x883 [ieee1394] > [...] > > This information confuses me. These places are not supposed to be the > ones where the locks were actually acquired, are they?
they should be yes (but inlined functions get the name of the function they are inlined into)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |