Linux NFS development
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 4/4] generic/633: Check if idmapped mounts are supported before running
Date: Tue,  8 Feb 2022 16:52:32 -0500	[thread overview]
Message-ID: <20220208215232.491780-5-anna@kernel.org> (raw)
In-Reply-To: <20220208215232.491780-1-anna@kernel.org>

From: Anna Schumaker <Anna.Schumaker@Netapp.com>

This appears to have been missed when the test was added.

Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
---
 tests/generic/633 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/generic/633 b/tests/generic/633
index 382806471223..6750117735f7 100755
--- a/tests/generic/633
+++ b/tests/generic/633
@@ -15,6 +15,7 @@ _begin_fstest auto quick atime attr cap idmapped io_uring mount perms rw unlink
 # real QA test starts here
 
 _supported_fs generic
+_require_idmapped_mounts
 _require_test
 
 echo "Silence is golden"
-- 
2.35.1


  parent reply	other threads:[~2022-02-08 22:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 21:52 [PATCH 0/4] Improvements for NFS Anna Schumaker
2022-02-08 21:52 ` [PATCH 1/4] check: Export CHECK_OPTIONS and PLATFORM for Xunit Reporting Anna Schumaker
2022-02-08 21:52 ` [PATCH 2/4] generic/531: Move test from 'quick' group to 'stress' Anna Schumaker
2022-02-23 16:54   ` Darrick J. Wong
2022-02-23 19:38     ` Anna Schumaker
2022-02-24  4:14       ` Darrick J. Wong
2022-02-08 21:52 ` [PATCH 3/4] generic/578: Test that filefrag is supported before running Anna Schumaker
2022-02-23 16:57   ` Darrick J. Wong
2022-02-23 18:24     ` Anna Schumaker
2022-02-24  4:15       ` Darrick J. Wong
2022-02-08 21:52 ` Anna Schumaker [this message]
2022-02-19  8:40   ` [PATCH 4/4] generic/633: Check if idmapped mounts are " Su Yue

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=20220208215232.491780-5-anna@kernel.org \
    --to=anna@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nfs@vger.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