public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guan@eryu.me>
To: Radoslav Kolev <radoslav.kolev@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: read only filesystem tests
Date: Sun, 21 Nov 2021 23:28:27 +0800	[thread overview]
Message-ID: <YZplm9Xo1lRKMJCN@desktop> (raw)
In-Reply-To: <e64129cb-dec9-f0bb-9a50-ede0a7b2aca6@suse.com>

On Mon, Nov 15, 2021 at 01:18:25PM +0200, Radoslav Kolev wrote:
> Hello,
> 
> I am interested in read only filesystem tests, and more specifically
> squashfs. I saw that ~2 year ago there was a patch set submitted, but not
> accepted that added support for it with some feedback, that
> the tests are copied and double the maintenance burden, but sadly there is
> no easy way to avoid that.
> 
> What is the current mood about read only filesystem tests and fstests?

I'd like to see tests for readonly filesystems, squashfs is definitely
one target, and other readonly filesystems like erofs could benefit from
the tests as well.

> Is this the right project to fill this need and is it worth it trying to
> address some of the problems with the old squashfs patches?

I think so, at least I'm happy to see readonly tests in fstests
personally. But, to be honest, I still didn't come out with a good way
to share existing generic tests for RO filesystems.. And I think it's a
good opportunity to use wisdom from the community :)

Thanks,
Eryu

  reply	other threads:[~2021-11-21 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 11:18 read only filesystem tests Radoslav Kolev
2021-11-21 15:28 ` Eryu Guan [this message]
2021-11-25 23:06 ` Dave Chinner

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=YZplm9Xo1lRKMJCN@desktop \
    --to=guan@eryu.me \
    --cc=fstests@vger.kernel.org \
    --cc=radoslav.kolev@suse.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