From: jing zhang Subject: Re: [PATCH] ext4: memory leakage in ext4_mb_init() Date: Mon, 5 Apr 2010 13:08:58 +0800 Message-ID: References: <87sk7nv4sp.fsf@linux.vnet.ibm.com> <20100403165340.GA17819@thunk.org> <20100404180845.GG18524@thunk.org> <4BB966AE.1060207@redhat.com> <4BB96E14.9010903@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: tytso@mit.edu, "Aneesh Kumar K. V" , linux-ext4 , Andreas Dilger , Dave Kleikamp To: Eric Sandeen Return-path: Received: from mail-yx0-f191.google.com ([209.85.210.191]:61720 "EHLO mail-yx0-f191.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750732Ab0DEFI7 (ORCPT ); Mon, 5 Apr 2010 01:08:59 -0400 Received: by yxe29 with SMTP id 29so1930545yxe.4 for ; Sun, 04 Apr 2010 22:08:58 -0700 (PDT) In-Reply-To: <4BB96E14.9010903@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: 2010/4/5, Eric Sandeen : > Testing really is critical to development; some things can be done by > inspection, but if you don't test it is hard to know if you made a > mistake. > > You can always test inside a vm, or on a loopback file, on a single box. > > Without testing, you are asking others to do testing for you > (unless the change is so obvious that it can be trusted) > Before linux-2.6.32 is released, would you like tell me, how is ext4 tested? Is tough testing able to catch all bugs? - zj