From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6EEA2C43381 for ; Mon, 11 Mar 2019 17:05:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 45E0E2075C for ; Mon, 11 Mar 2019 17:05:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727336AbfCKRF4 (ORCPT ); Mon, 11 Mar 2019 13:05:56 -0400 Received: from mx2.suse.de ([195.135.220.15]:60486 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727063AbfCKRF4 (ORCPT ); Mon, 11 Mar 2019 13:05:56 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 20FE9AFA7; Mon, 11 Mar 2019 17:05:55 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id BB2DE1E426A; Mon, 11 Mar 2019 18:05:53 +0100 (CET) Date: Mon, 11 Mar 2019 18:05:53 +0100 From: Jan Kara To: Steve Magnani Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Jan Kara , reinoud@netbsd.org, Colin King , =?utf-8?Q?Vojt=C4=9Bch?= Vladyka , linux-fsdevel@vger.kernel.org Subject: Re: [RFC] udftools: steps towards fsck Message-ID: <20190311170553.GQ11553@quack2.suse.cz> References: <17e5fea5-8d76-c96d-8902-9050acba4288@digidescorp.com> <20190307102349.q5not23mve2soope@pali> <1ebc384c-3944-9b7a-5b0e-bef5f78d9fdb@digidescorp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1ebc384c-3944-9b7a-5b0e-bef5f78d9fdb@digidescorp.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Fri 08-03-19 10:50:34, Steve Magnani wrote: > > > * For any standards-based parser it's important to have examples of as many > > > variations as possible (both normal and pathological) in order to ensure > > > that corner cases and less common features are tested properly. Can anyone > > > point me to any good sources of UDF data for testing? There are always > > > commercial DVDs and Blu-Ray discs, of course, and I've cobbled together a > > > few special cases by hand (i.e., a filesystem with directory cycles), but I > > > have no examples with extended attributes or stream data. If I could find a > > > DVD of Mac software in a resale shop would that help? [Side note, I've > > > thought of enhancing chkudf to support a tool that would store all the UDF > > > structures of a filesystem in a tarball that could be used to reconstitute > > > that filesystem within a sparse file. Since none of the file contents would > > > be stored the tarballs would be relatively small even if they represent > > > terabyte-scale filesystems. > Any thoughts on this? It would seem like a library of test cases would help > both udftools and kernel driver development. Agreed. E.g. e2fsprogs have a relatively large bunch of fs images to test fsck functionality. Initially I think it is important to have just several images checking basic functionality and an easy way to run them. New images to test then can be added as we find various corruptions in the wild... I have a couple of images I test the kernel driver against which I can contribute. Honza -- Jan Kara SUSE Labs, CR