linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: tytso@mit.edu
Cc: "Chris Mason" <clm@fb.com>, "Eric Sandeen" <sandeen@redhat.com>,
	"Lukáš Czerner" <lczerner@redhat.com>,
	dchinner@redhat.com, xfs@oss.sgi.com,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Separate mailing list for xfstests
Date: Wed, 14 May 2014 11:50:49 -0500	[thread overview]
Message-ID: <20140514165048.GA20454@boyd> (raw)
In-Reply-To: <20140514160447.GA3974@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On 2014-05-14 16:04:47, tytso@mit.edu wrote:
> On Wed, May 14, 2014 at 11:02:47AM -0400, Chris Mason wrote:
> > >> linux-fsdevel might seem as a good candidate for it, but still I
> > >> think that it deserves a separate ML to point people to.
> 
> I'm personally in favor of using linux-fsdevel since it might
> encourage more fs developers who aren't using xfstests yet to start
> using it.
> 
> For example, we started investigating using xfstests to test unionfs,
> and pretty quickly found problems.  (I suspect the same problem exists
> in AUFS, BTW, but I've been focusing on unionfs because it's simpler
> and less scary.)  The patches to enable the use of xfstests to test
> unionfs are still pretty rough, but hopefully we'll get those sent to
> Dave once they are cleaned up a bit.

Oh, that sounds interesting. I haven't seen these patches, but I expect
they would be pretty easy for me to extend for testing eCryptfs. That
has been on my todo list for a long time but I haven't spent much time
working on eCryptfs lately.

BTW, you can use this email as a supporting data point for your first
paragraph. :)

Tyler

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-05-14 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 13:20 Separate mailing list for xfstests Lukáš Czerner
2014-05-14 14:52 ` Eric Sandeen
2014-05-14 15:02   ` Chris Mason
2014-05-14 16:04     ` tytso
2014-05-14 16:50       ` Tyler Hicks [this message]
2014-05-14 21:35       ` Dave Chinner
2014-05-15 10:08         ` Lukáš Czerner
2014-05-14 21:46 ` Dave Chinner
2014-05-15 10:09   ` Lukáš Czerner

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=20140514165048.GA20454@boyd \
    --to=tyhicks@canonical.com \
    --cc=clm@fb.com \
    --cc=dchinner@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    --cc=xfs@oss.sgi.com \
    /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).