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 3/3] xfs: Add a testcase to check remount with noattr2 on a v5 xfs
Date: Wed, 19 Feb 2025 20:34:44 +0530 [thread overview]
Message-ID: <90be3350-67e5-4dec-bc65-442762f5f856@gmail.com> (raw)
In-Reply-To: <Z7O4MZ0xOpO_GTKE@dread.disaster.area>
On 2/18/25 03:59, Dave Chinner wrote:
> On Mon, Feb 17, 2025 at 10:18:48AM +0530, Nirjhar Roy (IBM) wrote:
>> On 2/14/25 03:19, Dave Chinner wrote:
>>> On Thu, Feb 13, 2025 at 03:30:50PM +0530, Nirjhar Roy (IBM) wrote:
>>>> On 2/13/25 03:17, Dave Chinner wrote:
>>>>> On Wed, Feb 12, 2025 at 12:39:58PM +0000, Nirjhar Roy (IBM) wrote:
>>> Ok, so CONFIG_XFS_SUPPORT_V4=n is the correct behaviour (known mount
>>> option, invalid configuration being asked for), and it is the
>>> CONFIG_XFS_SUPPORT_V4=y behaviour that is broken.
>> Okay, so do you find this testcase (patch 3/3 xfs: Add a testcase to check
>> remount with noattr2 on a v5 xfs) useful,
> Not at this point in time, because xfs/189 is supposed to exercise
> attr2/noattr2 mount/remount behaviour and take into account all the
> weirdness of the historic mount behaviour.
>
> Obviously, it is not detecting that this noattr2 remount behaviour
> was broken, so that test needs fixing/additions. Indeed, it's
> probably important to understand why xfs/189 isn't detecting this
> failure before going any further, right?
Yes. Let me look into what xfs/189 does and why it isn't detecting the
noattr2 remount broken behavior. Thank you for the pointer.
About "Patch 1/3: xfs/539: Skip noattr2 remount option on v5 file
systems" --> I wrote the patch because xfs/539 has started failing in
one of fstests CI runs because RHEL 10 has started disabling xfs v4
support i.e, CONFIG_XFS_SUPPORT_V4=n. Do you think modifying patch
1/3(xfs/539) 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)?
--NR
>
> IMO, it is better to fix existing tests that exercise the behaviour
> in question than it is to add a new test that covers just what the
> old test missed.
>
> -Dave.
--
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore
prev parent reply other threads:[~2025-02-19 15:04 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)
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) [this message]
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=90be3350-67e5-4dec-bc65-442762f5f856@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