Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 24 Nov 2002 17:25:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 24 Nov 2002 17:25:24 -0500 Received: from dp.samba.org ([66.70.73.150]:29867 "EHLO lists.samba.org") by vger.kernel.org with ESMTP id ; Sun, 24 Nov 2002 17:25:20 -0500 From: Rusty Russell To: "David S. Miller" Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au, torvalds@transmeta.com Subject: Re: calling schedule() from interupt context In-reply-to: Your message of "Fri, 22 Nov 2002 01:09:34 -0800." <20021122.010934.126934922.davem@redhat.com> Date: Mon, 25 Nov 2002 08:42:15 +1100 Message-Id: <20021124223234.7C5EB2C111@lists.samba.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 25 In message <20021122.010934.126934922.davem@redhat.com> you write: > 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? Err, no, that would be insane. get_cpu() & put_cpu() should work perfectly fine inside interrupts, no? > Egads... that makes lots of the networking stuff > nearly impossible as SKB's hold references to modules > and thus skb freeing can thus put modules. Relax: modular networking was one of my aims 8) Rusty. -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - 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/