Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Mar 2003 17:18:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Mar 2003 17:18:19 -0500 Received: from pcp02781107pcs.eatntn01.nj.comcast.net ([68.85.61.149]:29938 "EHLO linnie.riede.org") by vger.kernel.org with ESMTP id ; Sat, 15 Mar 2003 17:18:18 -0500 Date: Sat, 15 Mar 2003 17:29:17 -0500 From: Willem Riede To: Zwane Mwaikambo Cc: dan carpenter , Linux Kernel Subject: Re: Any hope for ide-scsi (error handling)? Message-ID: <20030315222917.GK7082@linnie.riede.org> Reply-To: wrlk@riede.org References: <200303151926.h2FJQLnB103490@pimout1-ext.prodigy.net> <200303152012.h2FKCulK283698@pimout2-ext.prodigy.net> <20030315210120.GI7082@linnie.riede.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7BIT In-Reply-To: ; from zwane@holomorphy.com on Sat, Mar 15, 2003 at 16:11:28 -0500 X-Mailer: Balsa 1.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 701 Lines: 15 On 2003.03.15 16:11 Zwane Mwaikambo wrote: > On Sat, 15 Mar 2003, Willem Riede wrote: > > > It may not be elegant to schedule(1) with the lock taken, but it > > does work. > > > > However, my latest patch doesn't seem to be applied, since in my > > version I have a set_current_state(TASK_INTERRUPTIBLE); before > > the schedule. > > Yeah but what happens when a task tries to acquire ide_lock? It gets to wait until I'm done. Regards, Willem Riede. - 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/