Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964884AbWBPUY7 (ORCPT ); Thu, 16 Feb 2006 15:24:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964900AbWBPUY7 (ORCPT ); Thu, 16 Feb 2006 15:24:59 -0500 Received: from smtp.osdl.org ([65.172.181.4]:8617 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S964884AbWBPUY6 (ORCPT ); Thu, 16 Feb 2006 15:24:58 -0500 Date: Thu, 16 Feb 2006 12:18:31 -0800 From: Andrew Morton To: Jes Sorensen Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] Notifier chain update: API changes Message-Id: <20060216121831.6904376c.akpm@osdl.org> In-Reply-To: References: X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 934 Lines: 24 Jes Sorensen wrote: > > >>>>> "Alan" == Alan Stern writes: > > Alan> The kernel's implementation of notifier chains is unsafe. There > Alan> is no protection against entries being added to or removed from > Alan> a chain while the chain is in use. The issues were discussed in > Alan> this thread: > > Alan> http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2 > > Hi, > > I was wondering if there was anything blocking this change from going > in? I'd quite like to see it as it would avoid me from inventing yet > another notifier chain implementation ;-) > It's still lurking in my to-apply folder - will get onto it soon. - 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/