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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 015F2C00140 for ; Fri, 12 Aug 2022 14:00:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238213AbiHLOAd (ORCPT ); Fri, 12 Aug 2022 10:00:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232085AbiHLOAc (ORCPT ); Fri, 12 Aug 2022 10:00:32 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E03EA32B9B; Fri, 12 Aug 2022 07:00:30 -0700 (PDT) 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-out1.suse.de (Postfix) with ESMTPS id 75C513F7DF; Fri, 12 Aug 2022 14:00:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1660312829; h=from:from:reply-to: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=mmMcxR3luXAAfZt0qQrsQU3WBRdPesjPfp6BxoGMRiI=; b=pXBfwu6vovlebYiTuPDJU5B3y+fUhFb5MmDxrm9WhviztSGTbnoOLz7O7/nEYSHx23GQHJ Xq6DOPbZwYKWJKwrT7GrizWOjt96bp6m2oISjaLfjyKtUFOpT8GuLXhdwdDnCZlcbqGIk9 JusymBeXY+tzH39FGQQeNxXGh1A+AGo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1660312829; h=from:from:reply-to: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=mmMcxR3luXAAfZt0qQrsQU3WBRdPesjPfp6BxoGMRiI=; b=6uCtk6YNqCWUvLTpVyDa++OKjN5XsbhWcBGJ9RUa5c2KtvQcKEI9bV+dO2d+7ocOtyD1ld UgJF/LSko6Qm3RBg== 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 348CE13AAE; Fri, 12 Aug 2022 14:00:29 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id VbQ4C/1c9mJ5PAAAMHmgww (envelope-from ); Fri, 12 Aug 2022 14:00:29 +0000 Date: Fri, 12 Aug 2022 16:00:26 +0200 From: Petr Vorel To: linux-block@vger.kernel.org, Jens Axboe , Jan Kara , Hannes Reinecke , linux-xfs@vger.kernel.org Cc: ltp@lists.linux.it Subject: Re: LTP test df01.sh detected different size of loop device in v5.19 Message-ID: Reply-To: Petr Vorel References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org [ Cc LTP ML, sorry for the noise ] Petr > > Hi all, > > LTP test df01.sh found different size of loop device in v5.19. > > Test uses loop device formatted on various file systems, only XFS fails. > > It randomly fails during verifying that loop size usage changes: > > grep ${TST_DEVICE} output | grep -q "${total}.*${used}" [1] > > How to reproduce: > > # PATH="/opt/ltp/testcases/bin:$PATH" df01.sh -f xfs # it needs several tries to hit > > df saved output: > > Filesystem 1024-blocks Used Available Capacity Mounted on > > ... > > /dev/loop0 256672 16208 240464 7% /tmp/LTP_df01.1kRwoUCCR7/mntpoint > > df output: > > Filesystem 1024-blocks Used Available Capacity Mounted on > > ... > > tmpfs 201780 0 201780 0% /run/user/0 > > /dev/loop0 256672 15160 241512 6% /tmp/LTP_df01.1kRwoUCCR7/mntpoint > > => different size > > df01 4 TFAIL: 'df -k -P' failed, not expected. > > Also 'df -T -P' fails. > > It might be a false positive / bug in the test, but it's at least a changed behavior. > > I was able to reproduce it on v5.19 distro kernels (openSUSE, Debian). > > I haven't bisected (yet), nor checked Jens' git tree (maybe it has been fixed). > Forget to note dmesg "operation not supported error" warning on *each* run (even > successful) on affected v5.19: > [ 5097.594021] loop0: detected capacity change from 0 to 524288 > [ 5097.658201] operation not supported error, dev loop0, sector 262192 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 0 > [ 5097.675670] XFS (loop0): Mounting V5 Filesystem > [ 5097.681668] XFS (loop0): Ending clean mount > [ 5097.956445] XFS (loop0): Unmounting Filesystem > Kind regards, > Petr > > Kind regards, > > Petr > > [1] https://github.com/linux-test-project/ltp/blob/f42f6f3b4671f447b743afe8612917ba4362b8a6/testcases/commands/df/df01.sh#L103-L110