Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Feb 2003 19:42:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Feb 2003 19:42:31 -0500 Received: from smtpzilla5.xs4all.nl ([194.109.127.141]:16910 "EHLO smtpzilla5.xs4all.nl") by vger.kernel.org with ESMTP id ; Fri, 14 Feb 2003 19:42:30 -0500 Date: Sat, 15 Feb 2003 01:51:52 +0100 (CET) From: Roman Zippel X-X-Sender: roman@serv To: Werner Almesberger cc: Rusty Russell , , , , Subject: Re: [RFC] Migrating net/sched to new module interface In-Reply-To: <20030214211226.I2092@almesberger.net> Message-ID: References: <20030214120628.208112C464@lists.samba.org> <20030214105338.E2092@almesberger.net> <20030214153039.G2092@almesberger.net> <20030214211226.I2092@almesberger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 802 Lines: 30 Hi, On Fri, 14 Feb 2003, Werner Almesberger wrote: > I though we were talking about > > static data_used_by_callbacks; > ... > register_foo(&stuff_with_callbacks); > ... > unregister_foo(&stuff_with_callbacks); > make_unusable(&data_used_by_callbacks) > ... > /* oops, we just got a callback */ > > ("data_used_by_callbacks" could be a pointer to kmalloc'ed > memory, etc.) > > This kind of problem seems to be understood well enough. Yes, and now compare how the solutions differ when the data is static and when it's allocated. bye, Roman - 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/