lkml.org 
[lkml]   [1996]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Networking Status pre #2
Date
From
Amazingly enough Alan Cox said:
>
> > > 1. double lock on device queue
> >
> > I have no idea. Is there an error message or way to tell?
>
> That is the error message people with the problem will see.


For the record, I used to see a lot of these but haven't lately
(and I've been looking for them).

Is it possible for a lock to occur from two different locations?
The current code allows you to determine where the second lock
occurs, but not the first. Or is it, depending on the
circumstance, possible only to be locked in one location (only
doing it twice?).

Would it be reasonable to add fields to the sock struct so that
every time it's locked, add __FILE__ and __LINE__ values so that
one could track where the first lock occured? For debugging
purposes only, of course.

I added such code myself, but since I've not seen a double lock
occuring, I can't tell if it's useful or not.

mrc
--
Mike Castle .-=NEXUS=-. Life is like a clock: You can work constantly
mcastle@cs.umr.edu and be right all the time, or not work at all
mcastle@umr.edu and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.039 / U:1.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site