All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
	ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
	zlang@kernel.org, david@fromorbit.com,
	nirjhar.roy.lists@gmail.com
Subject: [PATCH v2 0/1] xfs/539: Ignore remount failures on v5 xfs
Date: Tue,  4 Mar 2025 13:48:15 +0000	[thread overview]
Message-ID: <cover.1741094926.git.nirjhar.roy.lists@gmail.com> (raw)

The test just checks for the deprecation dmesg
warnings when remounted with noattr2 and ikeep, 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. The reason why it was not failing with CONFIG_XFS_SUPPORT_V4=y
is because remount was incorrectly succeeding - reason is explained in [2].

[v1] --> v2
 - Removed patch 2/3 and patch 3/3 for now,
 - For patch 1/3 - Ignore the mount failure instead of skipping noattr2.

[v1] https://lore.kernel.org/all/cover.1739363803.git.nirjhar.roy.lists@gmail.com/
[2] https://lore.kernel.org/all/Z65o6nWxT00MaUrW@dread.disaster.area/


Nirjhar Roy (IBM) (1):
  xfs/539: Ignore remount failures on v5 xfs

 tests/xfs/539 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--
2.34.1


             reply	other threads:[~2025-03-04 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 13:48 Nirjhar Roy (IBM) [this message]
2025-03-04 13:48 ` [PATCH v2 1/1] xfs/539: Ignore remount failures on v5 xfs Nirjhar Roy (IBM)
2025-04-01  4:40   ` Nirjhar Roy (IBM)
2025-04-01 19:58   ` Pavel Reichl
2025-04-04 14:31     ` 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=cover.1741094926.git.nirjhar.roy.lists@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.