From: Eric Biggers <ebiggers3@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH] generic: test that encrypted filenames are presented without collisions
Date: Tue, 16 May 2017 15:44:28 -0700 [thread overview]
Message-ID: <20170516224428.GE113464@gmail.com> (raw)
In-Reply-To: <20170504073008.GK7250@eguan.usersys.redhat.com>
On Thu, May 04, 2017 at 03:30:08PM +0800, Eryu Guan wrote:
> On Mon, May 01, 2017 at 05:15:24PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > [RFC for now since the kernel fixes are currently sitting in fscrypt/master and
> > haven't been merged to Linus's tree yet; I'll resend this once they're merged]
> >
> > Add a test which creates many similarly-named files in an encrypted
> > directory, then verifies they can be deleted without access to the
> > encryption key. This is a regression test for two related bugs which
> > caused presented names to "collide" and point to the wrong inodes.
> >
> > Cc: linux-fscrypt@vger.kernel.org
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> The test looks fine to me, it fails on ext4 with rm reporting "Structure
> needs cleaning".
>
> One minor issue is that rm reports too many failures (around 98000
> lines in my test)
>
> +rm: cannot remove '/mnt/testarea/scratch/edir/_SET,lbqVCybotHoHkKrq4xM7FtbuBCLY': Structure needs cleaning
>
> and that makes the output diff a bit harder to review, and takes too
> much space in 500.out.bad file unnecessarily (11M). Better to trim or
> limit the error log somehow, e.g. using "head -n 10"?
>
> Thanks,
> Eryu
Yes, I'll limit it to 10 error messages. Thanks!
Eric
prev parent reply other threads:[~2017-05-16 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 0:15 [PATCH] generic: test that encrypted filenames are presented without collisions Eric Biggers
2017-05-04 7:30 ` Eryu Guan
2017-05-16 22:44 ` Eric Biggers [this message]
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=20170516224428.GE113464@gmail.com \
--to=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fscrypt@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