Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932438AbVLMFC4 (ORCPT ); Tue, 13 Dec 2005 00:02:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932440AbVLMFCz (ORCPT ); Tue, 13 Dec 2005 00:02:55 -0500 Received: from omx3-ext.sgi.com ([192.48.171.20]:42664 "EHLO omx3.sgi.com") by vger.kernel.org with ESMTP id S932438AbVLMFCz (ORCPT ); Tue, 13 Dec 2005 00:02:55 -0500 X-Mailer: exmh version 2.6.3_20040314 03/14/2004 with nmh-1.1 From: Keith Owens To: Alan Stern cc: Andrew Morton , sekharan@us.ibm.com, ak@suse.de, Kernel development list Subject: Re: [RFC][PATCH 0/7]: Fix for unsafe notifier chain In-reply-to: Your message of "Thu, 08 Dec 2005 14:53:56 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Dec 2005 16:02:30 +1100 Message-ID: <7639.1134450150@kao2.melbourne.sgi.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 19 On Thu, 8 Dec 2005 14:53:56 -0500 (EST), Alan Stern wrote: >The code below defines three new data structures: atomic_notifier_head, >blocking_notifier_head, and raw_notifier_head. The first two correspond >to what we had in the earlier patch, and raw_notifier_head is almost the >same as the current implementation, with no locking or protection at all. Acked-By: Keith Owens I do not care how this problem is fixed, I am happy with any solution that (a) stops notify chains being racy and (b) allows users of notify_die() to be safely unloaded. - 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/