From: Eric Biggers <ebiggers3@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
fstests@vger.kernel.org, linux-mtd@lists.infradead.org,
richard@nod.at
Subject: Re: [PATCH 1/2] Add support for UBIFS
Date: Wed, 17 May 2017 11:45:35 -0700 [thread overview]
Message-ID: <20170517184535.GB91213@gmail.com> (raw)
In-Reply-To: <20170517115355.GE7250@eguan.usersys.redhat.com>
On Wed, May 17, 2017 at 07:53:55PM +0800, Eryu Guan wrote:
> On Wed, May 17, 2017 at 11:55:29AM +0200, David Oberhollenzer wrote:
> > This patch is mostly based on the previous attempts of Eric Biggers
> > and Dongsheng Yang at adding UBIFS support to xfstests.
> >
> > In addition to rebasing the previous attempts to recent xfstests,
> > most of the encryption tests now also support UBIFS with this patch.
> >
> > Since mkfs.ubifs doesn't support creating encryption-capable filesystems
> > yet, _scratch_mkfs_encrypted() is modified to wipe the underlying UBI
> > volume. The filesystem is then created when mounting the emtpy volume.
> >
> > Some tests that require SCRATCH_DEV to be a block device, despite
> > not using device-mapper or otherwise doing something block device
> > specific have that requirement removed.
> >
> > Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
>
> Thanks for the patch! I know only very little about ubifs (from previous
> reviews to attempts to add ubifs support to fstests), but it's still
> good to have some words to introduce ubifs briefly in commit log,
> especially the fact that it uses char device not block device.
>
> > ---
> > check | 2 ++
> > common/config | 7 +++++++
> > common/encrypt | 3 +++
> > common/rc | 24 ++++++++++++++++++++++++
> > tests/generic/076 | 1 -
> > tests/generic/409 | 1 -
> > tests/generic/410 | 1 -
> > tests/generic/411 | 1 -
> > 8 files changed, 36 insertions(+), 4 deletions(-)
> >
> > diff --git a/check b/check
> > index 9cef58b4..f8db3cd6 100755
> > --- a/check
> > +++ b/check
> > @@ -70,6 +70,7 @@ check options
> > -overlay test overlay
> > -pvfs2 test PVFS2
> > -tmpfs test TMPFS
> > + -ubifs test ubifs
> > -l line mode diff
> > -udiff show unified diff (default)
> > -n show me, do not run tests
> > @@ -267,6 +268,7 @@ while [ $# -gt 0 ]; do
> > -overlay) FSTYP=overlay; export OVERLAY=true ;;
> > -pvfs2) FSTYP=pvfs2 ;;
> > -tmpfs) FSTYP=tmpfs ;;
> > + -ubifs) FSTYP=ubifs ;;
>
> As being pointed out in previous reviews, it'll be great if we can probe
> ubifs from the char device if possible instead of adding new fs-specific
> option, just as what we're doing at the end of common/config for other
> local filesystems. But I'm not sure if blkid works for char device and
> ubifs (probably not).
>
It seems to work fine without the -ubifs option:
# blkid -o value -s TYPE /dev/ubi0_0
ubifs
# TEST_DEV=/dev/ubi0_0 TEST_DIR=/vdb ./check generic/001
FSTYP -- ubifs
PLATFORM -- Linux/x86_64 kvm-xfstests 4.12.0-rc1-xfstests-00083-ga844e08648f0-dirty
generic/001 [ 372.213194] run fstests generic/001 at 2017-05-17 11:43:47
8s
Ran: generic/001
Passed all 1 tests
- Eric
next prev parent reply other threads:[~2017-05-17 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 9:55 Add UBIFS support to xfstests David Oberhollenzer
2017-05-17 9:55 ` [PATCH 1/2] Add support for UBIFS David Oberhollenzer
2017-05-17 11:53 ` Eryu Guan
2017-05-17 18:45 ` Eric Biggers [this message]
2017-05-18 8:41 ` David Oberhollenzer
2017-05-18 11:35 ` Eryu Guan
2017-05-17 9:55 ` [PATCH 2/2] Accept failing with EPERM in addition to ENOKEY for rename without key David Oberhollenzer
2017-05-17 19:21 ` Eric Biggers
2017-05-17 9:55 ` [PATCH] xfstests-bld: add experimental support for ubifs David Oberhollenzer
2017-05-17 19:05 ` Add UBIFS support to xfstests Eric Biggers
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=20170517184535.GB91213@gmail.com \
--to=ebiggers3@gmail.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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