Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Nov 2002 04:09:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Nov 2002 04:09:06 -0500 Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com ([24.136.46.5]:1555 "EHLO svr-ganmtc-appserv-mgmt.ncf.coxexpress.com") by vger.kernel.org with ESMTP id ; Fri, 22 Nov 2002 04:09:05 -0500 Subject: Re: calling schedule() from interupt context From: Robert Love To: "David S. Miller" Cc: error27@email.com, linux-kernel@vger.kernel.org, rusty@rustcorp.com.au, torvalds@transmeta.com In-Reply-To: <20021122.010934.126934922.davem@redhat.com> References: <20021122085441.2127.qmail@email.com> <20021122.010934.126934922.davem@redhat.com> Content-Type: text/plain Organization: Message-Id: <1037956564.1504.3896.camel@phantasy> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 22 Nov 2002 04:16:04 -0500 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 704 Lines: 20 On Fri, 2002-11-22 at 04:09, David S. Miller wrote: > From: "dan carpenter" > Date: Fri, 22 Nov 2002 03:54:41 -0500 > > module_put ==> put_cpu ==> preempt_schedule ==> schedule > > Oh we can't kill module references from interrupts? No, I think you can. Or at least the put_cpu() will not hurt you. Inside the interrupt handlers, the preemption count is bumped so preempt_schedule() will never call schedule(). Robert Love - 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/