Date: Mon, 12 Jan 2004 10:19:46 +0100
From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Peter Yao <peter@exavio.com.cn>, linux-kernel@vger.kernel.org,
       linux-scsi@vger.kernel.org
Subject: Re: smp dead lock of io_request_lock/queue_lock patch
Message-ID: <20040112091946.GA29779@suse.de>
References: <4002CC23.6000105@exavio.com.cn> <1073898527.4428.1.camel@laptop.fenrus.com> <20040112091903.GD24638@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040112091903.GD24638@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 975
Lines: 27

On Mon, Jan 12 2004, Jens Axboe wrote:
> On Mon, Jan 12 2004, Arjan van de Ven wrote:
> > On Mon, 2004-01-12 at 17:32, Peter Yao wrote:
> > > Hi,
> > > I found a smp dead lock in io_request_lock/queue_lock patch in redhat's
> > > 2.4.18-4 kernel. 
> > 
> > 1) Bugs in vendor kernels are best reported to the vendor, in this case
> > in http://bugzilla.redhat.com
> > 2) 2.4.18-4 is really old and has been superceeded by updates a few
> > dozen times
> > 3) 2.4.18-4 has both remote and local security issues and datacorruption
> > issues
> 
> 4) The problem reported and patch looks real, though, maybe a little
> credit and thanks would be appropriate as well?

... and still exists in your 2.4.21 based kernel.

-- 
Jens Axboe

-
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/