Return-Path: Received: from lucidpixels.com ([72.73.18.11]:41801 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752372Ab1G2U7R (ORCPT ); Fri, 29 Jul 2011 16:59:17 -0400 Date: Fri, 29 Jul 2011 16:59:15 -0400 (EDT) From: Justin Piszcz To: Bryan Schumaker cc: Trond Myklebust , Christoph Hellwig , "J. Bruce Fields" , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop In-Reply-To: <4E331D86.7060801@netapp.com> Message-ID: References: <20110727160752.GC974@fieldses.org> <20110727181111.GA23009@infradead.org> <20110727193937.GA5354@infradead.org> <20110727194722.GA9345@infradead.org> <1311799021.25645.41.camel@lade.trondhjem.org> <1311800051.25645.43.camel@lade.trondhjem.org> <1311800195.25645.45.camel@lade.trondhjem.org> <1311886137.27285.2.camel@lade.trondhjem.org> <4E331D86.7060801@netapp.com> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 On Fri, 29 Jul 2011, Bryan Schumaker wrote: > How does this look for printing out more information when a cookie loop is detected? Is there anything else that should be printed out? My patch applies on top of Trond's from yesterday. Hi, This fails against 2.6.38: patching file fs/nfs/dir.c Hunk #1 FAILED at 134. Hunk #2 FAILED at 173. Hunk #3 FAILED at 323. Hunk #4 FAILED at 336. Hunk #5 FAILED at 349. Hunk #6 succeeded at 320 (offset -48 lines). Hunk #7 FAILED at 741. Hunk #8 succeeded at 716 (offset -59 lines). Hunk #9 succeeded at 749 (offset -59 lines). Hunk #10 succeeded at 763 (offset -59 lines). 6 out of 10 hunks FAILED -- saving rejects to file fs/nfs/dir.c.rej patching file include/linux/nfs_fs.h Hunk #1 FAILED at 99. 1 out of 1 hunk FAILED -- saving rejects to file include/linux/nfs_fs.h.rej atom:/usr/src/linux# And the 3.0 kernel is broken for my wireless adapter: http://www.gossamer-threads.com/lists/linux/kernel/1411576 If you can make a combined patch for 2.6.38 I can try it, 2.6.39+ have a horrible driver (rt2800usb) and 1 person emailed me as well stating the same thing off-list (they stick with the manufacturer's driver or the *sta one). Justin.