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 B155FC352A1 for ; Tue, 6 Dec 2022 18:01:45 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id 536FB3CDBDC for ; Tue, 6 Dec 2022 19:01:42 +0100 (CET) Received: from in-3.smtp.seeweb.it (in-3.smtp.seeweb.it [IPv6:2001:4b78:1:20::3]) (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 4F8FC3C7621 for ; Tue, 6 Dec 2022 19:01:33 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (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-3.smtp.seeweb.it (Postfix) with ESMTPS id 4D38C1A0034A for ; Tue, 6 Dec 2022 19:01:31 +0100 (CET) Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (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-out1.suse.de (Postfix) with ESMTPS id 7320921C54; Tue, 6 Dec 2022 18:01:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1670349691; 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=KUvattl1vOeajy5RTiXUN115kmAyvdmSnX5eY4J6xDU=; b=X8A58WR8C63lY8kC5hF+XHTzt5TNq/kQW2u8TzCDRZHkN7oHOn6vJNavRL8O+2feykkdMw s3sX0GXVI57TbRHfeuGumjioRmuObLjDLMHVFf5sC1LJZs7qjaqX2mcYG8/RHZxZMl6yB1 j/u13+5y8dBE1dOJCHH3R1RgemKNBvs= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1670349691; 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=KUvattl1vOeajy5RTiXUN115kmAyvdmSnX5eY4J6xDU=; b=EXRjGDtPEhfNPXofnarnTyXVSVIpSjVVr80PKqZEIx++eu7g8k7gnRuHMS4xdExzgl1VSK QqDGV9mg0t67UsDQ== Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (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 imap1.suse-dmz.suse.de (Postfix) with ESMTPS id 050AF13326; Tue, 6 Dec 2022 18:01:30 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap1.suse-dmz.suse.de with ESMTPSA id smXnMnqDj2NYFwAAGKfGzw (envelope-from ); Tue, 06 Dec 2022 18:01:30 +0000 Date: Tue, 6 Dec 2022 19:02:47 +0100 From: Cyril Hrubis To: Richard Palethorpe Message-ID: References: <20221206115329.17760-1-rpalethorpe@suse.com> <20221206115329.17760-2-rpalethorpe@suse.com> <87edtctuos.fsf@suse.de> <87a640trg1.fsf@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87a640trg1.fsf@suse.de> X-Virus-Scanned: clamav-milter 0.102.4 at in-3.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [PATCH 2/2] fill_fs: Ensure written data is not easily compressed 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: 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! > What are we trying to do though, simply fill the device to test the > ENOSPC condition or some kind of poor man's fuzzing? The test is supposed to test what happens when filesystem is altmost full and being written to, which may trigger all kinds of corner cases. In that sense it makes sense to randomize the access patterns a bit so that we have higher chances of utilizing different code paths. But of course the question where should we stop in randomizing things and what makes sense and what does not. -- Cyril Hrubis chrubis@suse.cz -- Mailing list info: https://lists.linux.it/listinfo/ltp