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 Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 77C19ECAAD8 for ; Fri, 16 Sep 2022 13:15:47 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id 5694B3CACB2 for ; Fri, 16 Sep 2022 15:15:45 +0200 (CEST) Received: from in-5.smtp.seeweb.it (in-5.smtp.seeweb.it [217.194.8.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id ACE953CAC18 for ; Fri, 16 Sep 2022 15:15:34 +0200 (CEST) Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-5.smtp.seeweb.it (Postfix) with ESMTPS id 1CDD160177A for ; Fri, 16 Sep 2022 15:15:33 +0200 (CEST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 1665E205A3; Fri, 16 Sep 2022 13:15:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1663334133; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eIb/M8gSVAxo6loI98XBPWZInLQ1DXfHU58UaJtYvoE=; b=du9ifSjXSvQWiWpEFX94xwRVR7GbcSs9Yvp6hUOhOviXYSSGfk+kuNRm8Z00rY3DvMvxlv xNvmIC8RlN8e0nb9qdv7nxoB+Wt/iIyDXrvCNY9uWetSUuh7IS3EQk7NQHdLLdEz/tOiK0 +M92brTKhrD9pbOs+/ZpQaxY7jvZFl8= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1663334133; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eIb/M8gSVAxo6loI98XBPWZInLQ1DXfHU58UaJtYvoE=; b=w5cLDMgB47hDc2bNugpzrYwRmoKIN55/bwJE8s1PkldNr7OOEfN0Ruai+bT9NbhnvN6xwO 3mi28PMJUF5yobAQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id EBB5B1346B; Fri, 16 Sep 2022 13:15:32 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id F6bTN/R2JGO6OwAAMHmgww (envelope-from ); Fri, 16 Sep 2022 13:15:32 +0000 Date: Fri, 16 Sep 2022 15:17:30 +0200 From: Cyril Hrubis To: Petr Vorel Message-ID: References: <20220915093639.2261-1-pvorel@suse.cz> <20220915093639.2261-6-pvorel@suse.cz> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Virus-Scanned: clamav-milter 0.102.4 at in-5.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [PATCH v6 5/8] tst_test.sh: Add $TST_ALL_FILESYSTEMS X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Richard Palethorpe , ltp@lists.linux.it Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" Hi! > > Whatever the API ends up I guess that we should check the support and > > mkfs here as well in order to TCONF early before we create a device and > > attempt to format/mount it. > I was worried to add mkfs.foo dependency unless there is a requirement for it > (i.e. TST_NEEDS_DEVICE=1). Do you really want to add this dependency for *all* > tests? (I'd prefer no, i.e. to keep here check only for test not being skipped, > because check for mkfs.foo is in tst_mkfs which does the job, thus not only we'd > add an extra unneeded dependency but also duplicity in the check). Isn't this mostly theoretical problem? I mean how common it would be to have test that tests different filesystem but does not need corresponding mkfs? > But if you want it, i.e. if we require mkfs.$TST_FS_TYPE (unless tmpfs of > course, which is handled properly) here, then we don't need to separate checks > for mkfs.foo and skip list in testcases/lib/tst_supported_fs.c. I would go that way for now. I guess that the cleanest solution would be keeping the funcionality really orthogonal, i.e. separating the kernel and mkfs checks so that we would have -m to enable mkfs check -k to enable kernel check and -s to enable skiplist. But that is something that can and should be done after the relase. -- Cyril Hrubis chrubis@suse.cz -- Mailing list info: https://lists.linux.it/listinfo/ltp