FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
	ojaswin@linux.ibm.com, djwong@kernel.org, zlang@kernel.org
Subject: Re: [PATCH v1 1/3] xfs/539: Skip noattr2 remount option on v5 filesystems
Date: Mon, 24 Feb 2025 10:20:49 +0530	[thread overview]
Message-ID: <8b927d46-f34f-4ae5-96df-835c40a6f574@gmail.com> (raw)
In-Reply-To: <Z60MMI3mbC9ou6rC@dread.disaster.area>


On 2/13/25 02:31, Dave Chinner wrote:
> On Wed, Feb 12, 2025 at 12:39:56PM +0000, Nirjhar Roy (IBM) wrote:
>> This test is to verify that repeated warnings are not printed
>> for default options (attr2, noikeep) and warnings are
>> printed for non default options (noattr2, ikeep). Remount
>> with noattr2 fails on a v5 filesystem, so skip the mount option.
> Why do we care if remount succeeds or fails? That's not what the
> test is exercising.
>
> i.e. We are testing to see if the appropriate deprecation warning
> for a deprecated mount option has been issued or not, and that
> should happen regardless of whether the mount option is valid or not
> for the given filesysetm format....
>
> Hence I don't see any reason for changing the test to exclude
> noattr2 testing on v5 filesystems...

Yes, this makes sense. The test indeed just checks for the dmesg 
warnings, and they appear even if the remount fails. I wrote the patch 
because xfs/539 has started failing in one of our fstests CI runs 
because RHEL 10 has started disabling xfs v4 support i.e, 
CONFIG_XFS_SUPPORT_V4=n. Do you think modifying this patch in such a way 
that the test ignores the remount failures with noattr2 and continues 
the test is an appropriate idea (since the test xfs/539 only intends to 
check the dmesg warnings)? So something like:,

--- a/tests/xfs/539
+++ b/tests/xfs/539
@@ -61,7 +61,11 @@ for VAR in {attr2,noikeep}; do
  done
  for VAR in {noattr2,ikeep}; do
      log_tag
-    _scratch_remount $VAR
+    _scratch_remount $VAR >> $seqres.full 2>&1
+    if [[ "$VAR" == "noattr2" && "$?" != "0" ]]; then
+        echo "remount will fail in v5 filesystem but the warning should 
be printed" \
+            >> $seqres.full
+    fi
      check_dmesg_for_since_tag "XFS: $VAR mount option is deprecated" || \
          echo "Could not find deprecation warning for $VAR"

I also suggested something similar in one of my previous replies[1] in 
this patch series. Can you please let me know your thoughts on this?

[1] 
https://lore.kernel.org/all/90be3350-67e5-4dec-bc65-442762f5f856@gmail.com/

--NR

>
> -Dave.

-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


  parent reply	other threads:[~2025-02-24  4:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 12:39 [PATCH v1 0/3] Add mount and remount related tests Nirjhar Roy (IBM)
2025-02-12 12:39 ` [PATCH v1 1/3] xfs/539: Skip noattr2 remount option on v5 filesystems Nirjhar Roy (IBM)
2025-02-12 21:01   ` Dave Chinner
2025-02-13 10:08     ` Nirjhar Roy (IBM)
2025-02-24  4:50     ` Nirjhar Roy (IBM) [this message]
2025-02-12 21:06   ` Darrick J. Wong
2025-02-12 12:39 ` [PATCH v1 2/3] common/xfs: Add a new helper function to check v5 XFS Nirjhar Roy (IBM)
2025-02-12 21:23   ` Dave Chinner
2025-02-12 12:39 ` [PATCH v1 3/3] xfs: Add a testcase to check remount with noattr2 on a v5 xfs Nirjhar Roy (IBM)
2025-02-12 21:47   ` Dave Chinner
2025-02-13 10:00     ` Nirjhar Roy (IBM)
2025-02-13 21:49       ` Dave Chinner
2025-02-17  4:48         ` Nirjhar Roy (IBM)
2025-02-17 22:29           ` Dave Chinner
2025-02-19 15:04             ` Nirjhar Roy (IBM)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8b927d46-f34f-4ae5-96df-835c40a6f574@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=zlang@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox