public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [PATCH 5/5] generic/623: add overlay into the blacklist
Date: Sun, 29 May 2022 18:55:05 +0800	[thread overview]
Message-ID: <20220529105505.667891-6-zlang@kernel.org> (raw)
In-Reply-To: <20220529105505.667891-1-zlang@kernel.org>

The _require_scratch_shutdown can't help this test case, except use
_scratch_shutdown or _scratch_shutdown_handle with it. But this test
case does 'shutdown' on $SCRATCH_MNT/file directly. It's not suitable
for overlay.

Signed-off-by: Zorro Lang <zlang@kernel.org>
---
 tests/generic/623 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/generic/623 b/tests/generic/623
index ea016d91..1083e796 100755
--- a/tests/generic/623
+++ b/tests/generic/623
@@ -11,7 +11,7 @@ _begin_fstest auto quick shutdown
 
 . ./common/filter
 
-_supported_fs generic
+_supported_fs ^overlay
 _fixed_by_kernel_commit e4826691cc7e \
 	"xfs: restore shutdown check in mapped write fault path"
 
-- 
2.31.1


  parent reply	other threads:[~2022-05-29 10:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 10:55 [PATCH 0/5] random fixes for fstests Zorro Lang
2022-05-29 10:55 ` [PATCH 1/5] generic/139: require 512 bytes to be the minimum dio size Zorro Lang
2022-05-30  0:11   ` Dave Chinner
2022-05-29 10:55 ` [PATCH 2/5] generic/506: call _require_quota before _qmount Zorro Lang
2022-05-30  0:12   ` Dave Chinner
2022-05-29 10:55 ` [PATCH 3/5] generic/591: remove redundant output from golden image Zorro Lang
2022-05-30  0:44   ` Dave Chinner
2022-05-30  5:43     ` Zorro Lang
2022-05-29 10:55 ` [PATCH 4/5] generic/591: use proper sector size Zorro Lang
2022-05-29 23:57   ` Dave Chinner
2022-05-30  6:02     ` Zorro Lang
2022-05-29 10:55 ` Zorro Lang [this message]
2022-05-30  5:54   ` [PATCH 5/5] generic/623: add overlay into the blacklist Amir Goldstein
2022-05-30  6:22     ` Zorro Lang

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=20220529105505.667891-6-zlang@kernel.org \
    --to=zlang@kernel.org \
    --cc=fstests@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