From: Eric Biggers <ebiggers3@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
David Gstir <david@sigma-star.at>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@google.com>
Subject: [RFC][PATCH 0/2] xfstests on ubifs
Date: Mon, 19 Dec 2016 10:45:30 -0800 [thread overview]
Message-ID: <1482173132-100690-1-git-send-email-ebiggers3@gmail.com> (raw)
From: Eric Biggers <ebiggers@google.com>
Hello,
Since ubifs encryption has been merged into the 4.10 kernel, I wanted to run my
new encryption tests on ubifs to make sure it's compatible with ext4 and f2fs.
xfstests doesn't support ubifs yet but I was able to hack something together.
I'm sending my patches for anyone who may be interested.
The first patch adds ubifs support to xfstests itself. This is a fairly small
patch that just deals with a couple quirks of ubifs, e.g. requiring a char
device rather than a block device.
The second patch updates xfstests-bld (a separate project maintained by Theodore
Ts'o) to support ubifs with kvm-xfstests and gce-xfstests. It uses block2mtd to
emulate MTD devices using standard block devices, then layers UBI volumes on top
of these. Of course, actually running the tests is dependent on the xfstests
patch.
Note: I'm *not* an ubifs developer, and so far I haven't done much else besides
run the encryption tests. There seemed to be a lot of failures when I tried
running some of the other generic xfstests, and also a strange failure in the
encryption test generic/402 that I wasn't able to fix; so if I haven't obviously
screwed something up, I strongly suggest the ubifs developers look into this.
Note 2: since mkfs.ubifs doesn't support creating encryption-capable filesystems
yet (ubifs v5), to get the encryption tests to work I also had to hack
_scratch_mkfs_encrypted() to use ubirmvol/ubimkvol instead of mkfs. I assume
that the ubifs developers are planning to update mkfs.ubifs.
Eric
next reply other threads:[~2016-12-19 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 18:45 Eric Biggers [this message]
2016-12-19 18:45 ` [RFC][PATCH 1/2] xfstests: add experimental support for ubifs Eric Biggers
2016-12-19 18:45 ` [RFC][PATCH 2/2] xfstests-bld: " Eric Biggers
2016-12-19 19:12 ` [RFC][PATCH 0/2] xfstests on ubifs Richard Weinberger
2016-12-19 19:25 ` Eric Biggers
2016-12-19 21:31 ` Eric Biggers
2016-12-19 19:48 ` Richard Weinberger
2016-12-19 19:59 ` Eric Biggers
2016-12-19 20:02 ` Richard Weinberger
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=1482173132-100690-1-git-send-email-ebiggers3@gmail.com \
--to=ebiggers3@gmail.com \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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