Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264879AbTFLQeW (ORCPT ); Thu, 12 Jun 2003 12:34:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264880AbTFLQeW (ORCPT ); Thu, 12 Jun 2003 12:34:22 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:32524 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S264879AbTFLQeW (ORCPT ); Thu, 12 Jun 2003 12:34:22 -0400 Date: Thu, 12 Jun 2003 09:47:46 -0700 (PDT) From: Linus Torvalds To: Dipankar Sarma cc: John M Flinchbaugh , , Trond Myklebust , Maneesh Soni , Andrew Morton Subject: Re: 2.5.70-bk16: nfs crash In-Reply-To: <20030612163527.GD1438@in.ibm.com> Message-ID: 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: 808 Lines: 21 On Thu, 12 Jun 2003, Dipankar Sarma wrote: > > That should work. However, I do have once concern. At the generic > list macro level, we don't know if the lockfree traversal is being > done in forward or backward direction. Sure we do. We do have backwards list traversal, but it's already not available for the RCU case (ie we have "list_for_each_entry_rcu()", but we don't have "list_for_each_entry_reverse_rcu()"). Of course, somebody may be using the non-RCU versions of the list traversal macros on a RCU list, but that would be a bug anyway. Linus - 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/