linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: Testing Ext4 encryption with fstests
Date: Sat, 02 Dec 2017 08:44:29 +0530	[thread overview]
Message-ID: <2008991.n3x73QCyP8@localhost.localdomain> (raw)

Hi,

I have now got an initial version of patch to get encryption to work on
blocksize < pagesize
(https://github.com/chandanr/linux/commit/343ef14a6c33fd3fc4bda11a2ffa6de8cd695f04).
There is still some error handling code to be written.

My fstests local.config has,

export TEST_DEV=/dev/loop0
export TEST_DIR=/mnt/btrfs-xfstest-test
export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=/mnt/btrfs-xfstest-scratch
MKFS_OPTIONS="-O encrypt"
EXT_MOUNT_OPTIONS="-o test_dummy_encryption"
export FSTYPE=ext4

With the latest linux-next next-20171201 (i.e. without my changes applied)
on x86 I see some tests fail and also filesystem consistency almost always 
fails. E.g.

_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//check.full for details)
generic/011 1s ... 0s
_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//generic/011.full for details)
Ran: generic/011
Failures: generic/011
Failed 1 of 1 tests

FSTYP         -- ext4
PLATFORM      -- Linux/x86_64 localhost 4.13.0-next-20170905-gf165385
MKFS_OPTIONS  -- -O encrypt /dev/loop1
MOUNT_OPTIONS -- -o acl,user_xattr -o test_dummy_encryption /dev/loop1 /mnt/btrfs-xfstest-scratch

_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//check.full for details)
generic/012 0s ... [failed, exit status 1] - output mismatch (see /root/xfstests-dev/results//generic/012.out.bad)
    --- tests/generic/012.out   2016-11-22 09:11:59.000000000 +0530
    +++ /root/xfstests-dev/results//generic/012.out.bad 2017-12-01 11:14:08.826594934 +0530
    @@ -47,3 +47,5 @@
        14. data -> hole @ 0
     0: [0..95]: extent
     f1894a71ac539f6f90426d98a4990a47
    +_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
    +(see /root/xfstests-dev/results//generic/012.full for details)
    ...
    (Run 'diff -u tests/generic/012.out /root/xfstests-dev/results//generic/012.out.bad'  to see the entire diff)
_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//generic/012.full for details)
Ran: generic/012
Failures: generic/012
Failed 1 of 1 tests

FSTYP         -- ext4
PLATFORM      -- Linux/x86_64 localhost 4.13.0-next-20170905-gf165385
MKFS_OPTIONS  -- -O encrypt /dev/loop1
MOUNT_OPTIONS -- -o acl,user_xattr -o test_dummy_encryption /dev/loop1 /mnt/btrfs-xfstest-scratch


_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//check.full for details)
generic/013 2s ... [failed, exit status 1] - output mismatch (see /root/xfstests-dev/results//generic/013.out.bad)
    --- tests/generic/013.out   2016-11-22 09:11:59.000000000 +0530
    +++ /root/xfstests-dev/results//generic/013.out.bad 2017-12-01 11:14:09.724595573 +0530
    @@ -1,14 +1,5 @@
     QA output created by 013
     brevity is wit...
    -
    ------------------------------------------------
    -fsstress.1 : -r
    ------------------------------------------------
    -
    ...
    (Run 'diff -u tests/generic/013.out /root/xfstests-dev/results//generic/013.out.bad'  to see the entire diff)
_check_generic_filesystem: filesystem on /dev/loop0 is inconsistent
(see /root/xfstests-dev/results//generic/013.full for details)
Ran: generic/013
Failures: generic/013
Failed 1 of 1 tests

Please let me know if the test setup described above is incorrect.

-- 
chandan

             reply	other threads:[~2017-12-02  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02  3:14 Chandan Rajendra [this message]
2017-12-03  2:44 ` Testing Ext4 encryption with fstests Theodore Ts'o
2017-12-03  6:22   ` Eryu Guan

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=2008991.n3x73QCyP8@localhost.localdomain \
    --to=chandan@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).