Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Feb 2003 12:06:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Feb 2003 12:06:39 -0500 Received: from havoc.daloft.com ([64.213.145.173]:42645 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id ; Thu, 20 Feb 2003 12:06:38 -0500 Date: Thu, 20 Feb 2003 12:16:38 -0500 From: Jeff Garzik To: Steven French Cc: Martin Josefsson , linux-kernel@vger.kernel.org Subject: Re: cifs leaks memory like crazy in 2.5.61 Message-ID: <20030220171638.GC9800@gtf.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 981 Lines: 24 On Thu, Feb 20, 2003 at 10:56:04AM -0600, Steven French wrote: > I run three file API tests regularly against it - fsx, the connecathon > "nfs" tests and iozone and use them as a sort of regression test bucket > (which unfortunately didn't pick this problem up) - as a result of this I > will add "ls -R" of a deep directory tree to the list (ls -R of a shallow > tree doesn't seem to show this problem up) - if there are other useful > filesystem regression cases that I could automate and run, I would love to > know about them. Those are more stress tests, than regression tests. You have to know what you regressed from, and progressed to, before you have regression tests. ;-) It sounds like unit tests are lacking... Jeff - 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/