public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Yang Erkun <yangerkun@huawei.com>
To: <hch@infradead.org>, <zlang@kernel.org>
Cc: <fstests@vger.kernel.org>, <linux-mm@kvack.org>,
	<hughd@google.com>, <akpm@linux-foundation.org>,
	<yoyang@redhat.com>, <yangerkun@huawei.com>
Subject: [PATCH v2 2/2] generic/732: don't run it on tmpfs
Date: Mon, 29 Jul 2024 16:47:15 +0800	[thread overview]
Message-ID: <20240729084715.1736839-2-yangerkun@huawei.com> (raw)
In-Reply-To: <20240729084715.1736839-1-yangerkun@huawei.com>

Like what 4fd042e0465c("generic/732: don't run it on NFS") say, the same
options for tmpfs won't share the same backend. Skip it for tmpfs.

Besides, add some explanation for why we should skip tmpfs.

Signed-off-by: Yang Erkun <yangerkun@huawei.com>
---
 tests/generic/732 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/generic/732 b/tests/generic/732
index d8475cda..d08028c2 100755
--- a/tests/generic/732
+++ b/tests/generic/732
@@ -21,7 +21,10 @@ _cleanup()
 	rm -r -f $tmp.*
 }
 
-_supported_fs ^nfs ^overlay
+# This case give a assumption that the same mount options for
+# different mount point will share the same superblock, which won't
+# sucess for the follow fs.
+_supported_fs ^nfs ^overlay ^tmpfs
 
 _require_test
 _require_scratch
-- 
2.39.2



  reply	other threads:[~2024-07-29  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  8:47 [PATCH v2 1/2] generic/732: remove unused code Yang Erkun
2024-07-29  8:47 ` Yang Erkun [this message]
2024-07-29 14:16   ` [PATCH v2 2/2] generic/732: don't run it on tmpfs Christoph Hellwig
2024-07-29 14:21     ` Chuck Lever III
2024-07-29 14:24       ` Chuck Lever III
2024-07-29 14:30         ` yangerkun
2024-07-29 14:28       ` yangerkun
2024-07-29 14:16 ` [PATCH v2 1/2] generic/732: remove unused code Christoph Hellwig

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=20240729084715.1736839-2-yangerkun@huawei.com \
    --to=yangerkun@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=yoyang@redhat.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