X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7E506.6347AF4A@onstor-exch02.onstor.net>; Wed, 22 Aug 2007 13:50:00 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: pleeze review
Date: Wed, 22 Aug 2007 13:49:59 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E051AECAB@onstor-exch02.onstor.net>
In-Reply-To: <20070822144639.43699ebc@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: pleeze review
Thread-Index: AcflBeu+EG1MujfwSHG2+/gLwhJJswAAEnDg
References: <20070822133943.32a19c20@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E051AEC32@onstor-exch02.onstor.net> <20070822144639.43699ebc@ripper.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

>
>> 1752: This is going to deadlock with itself.
>
>i sure hope not.  the driver doesn't use interrupts when in "console"
>mode; the idea is to flush any previously queued output (and interrupt
>states) when console write is called.
[MK]=20
The code gets a spinlock, then calls mpsc_tx_intr(), which is going to
try to get a spinlock again. How this will not deadlock?


