From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from e31.co.us.ibm.com ([32.97.110.149]:60691 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753403AbYDSXdl (ORCPT ); Sat, 19 Apr 2008 19:33:41 -0400 Date: Sat, 19 Apr 2008 16:33:38 -0700 From: "Paul E. McKenney" To: Johannes Berg Cc: linux-kernel@vger.kernel.org, Josh Triplett , linux-wireless@vger.kernel.org, linux-sparse@vger.kernel.org Subject: Re: [RFC 0/3] Examples for the new sparse context tracking functionality Message-ID: <20080419233338.GG20138@linux.vnet.ibm.com> (sfid-20080420_003348_051324_299498FE) Reply-To: paulmck@linux.vnet.ibm.com References: <20080410134810.629048000@sipsolutions.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20080410134810.629048000@sipsolutions.net> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Apr 10, 2008 at 03:48:10PM +0200, Johannes Berg wrote: > Here are some patches that show how the new sparse functionality > could be used in the kernel if merged. > > As mentioned before, I have actually found three bugs in mac80211 > using these patches. If you apply them and the sparse patches I have > also just posted, you can find them too :) I like this approach in general, deferring to Josh on specifics. At some point in the future, we might want to distinguish between the different flavors of RCU -- except that there is already common code that doesn't care which flavor of RCU is in use, as long as some sort of RCU is present. So make that "some point in the distant future"... Thanx, Paul