From: Theodore Ts'o Subject: Re: NULL pointer dereference in ext4_ext_remove_space on 3.5.1 Date: Fri, 17 Aug 2012 16:34:38 -0400 Message-ID: <20120817203438.GA573@thunk.org> References: <20120816024654.GB3781@thunk.org> <20120816111051.GA16036@localhost> <20120816152513.GA31346@thunk.org> <20120817060110.GA28786@localhost> <20120817131558.GA11439@thunk.org> <20120817174841.GA4519@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: xfs@oss.sgi.com, ext4 hackers To: Christoph Hellwig Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:45340 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756436Ab2HQUex (ORCPT ); Fri, 17 Aug 2012 16:34:53 -0400 Content-Disposition: inline In-Reply-To: <20120817174841.GA4519@infradead.org> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Fri, Aug 17, 2012 at 01:48:41PM -0400, Christoph Hellwig wrote: > > Can you submit this for xfstests? > This is actually something I wanted to ask you guys about. There are a series of ext4-specific tests that I could potentially add, but I wasn't sure how welcome they would be in xfstests. Assuming that ext4-specific tests would be welcome, is there a number range for these ext4-specific tests that I should use? BTW, we have an extension to xfstests that we've been using inside Google where Google-internal tests have a "g" prefix (i.e., g001, g002, etc.). That way we didn't need to worry about conflicts between newly added upstream xfstests, and ones which were added internally. Would it make sense to start using some kind of prefix such as "e001" for ext2/3/4 specific tests? Regards, - Ted