From: Jan Kara <jack@suse.cz>
To: fstests@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] fstests: Improve tmpfs handling
Date: Mon, 26 Apr 2021 22:50:10 +0200 [thread overview]
Message-ID: <20210426205012.13241-1-jack@suse.cz> (raw)
Hello,
when testing tmpfs with fstests, I've noticed a couple of fstests failures
which are bugs in tests (usually expecting functionality tmpfs does not
provide). The following two patches fix them.
Honza
next reply other threads:[~2021-04-26 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 20:50 Jan Kara [this message]
2021-04-26 20:50 ` [PATCH 1/2] common: Fix recovery tests for tmpfs Jan Kara
2021-04-26 20:50 ` [PATCH 2/2] Don't run tests that require block devices for virtual filesystems Jan Kara
2021-04-27 6:43 ` Amir Goldstein
2021-04-27 8:49 ` Jan Kara
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=20210426205012.13241-1-jack@suse.cz \
--to=jack@suse.cz \
--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