From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 28 May 2002 16:45:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 28 May 2002 16:44:00 -0400 Received: from [195.39.17.254] ([195.39.17.254]:64412 "EHLO Elf.ucw.cz") by vger.kernel.org with ESMTP id ; Tue, 28 May 2002 16:43:03 -0400 Date: Mon, 27 May 2002 13:44:14 +0000 From: Pavel Machek To: "Peter T. Breuer" Cc: Steve Whitehouse , linux kernel , alan@lxorguk.ukuu.org.uk, chen_xiangping@emc.com Subject: Re: Kernel deadlock using nbd over acenic driver Message-ID: <20020527134413.E35@toy.ucw.cz> In-Reply-To: <200205241011.LAA26311@gw.chygwyn.com> <200205241143.g4OBh1332485@oboe.it.uc3m.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > Look in some of the block drivers, floppy.c or loop.c. These do call > the task queue, even though that's only as an aid to the rest of the > kernel, because they know they can help at that point, and it's not at > all clear what context they're in. Perhaps it's best to look in > floppy.c, which runs the task queue in its init routine! I mean to say Init routine is called from insmod context or at kernel bootup (from pid==1). Both look like process context to me. Pavel -- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.