public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
	fstests@vger.kernel.org, Eryu Guan <eguan@redhat.com>
Subject: Re: ext4 quota tests fail with CONFIG_QFMT_V2=n
Date: Thu, 18 Jan 2018 10:07:28 -0800	[thread overview]
Message-ID: <20180118180728.GD10877@vader> (raw)
In-Reply-To: <20180118122125.pxgqttayxu6msdgl@quack2.suse.cz>

On Thu, Jan 18, 2018 at 01:21:25PM +0100, Jan Kara wrote:
> On Wed 17-01-18 20:28:31, Theodore Ts'o wrote:
> > On Wed, Jan 17, 2018 at 05:09:36PM -0800, Omar Sandoval wrote:
> > > Hello,
> > > 
> > > If I run xfstests on ext4 with a kernel with CONFIG_QFMT_V2=n, the following
> > > tests fail:
> > > 
> > > generic/082
> > > generic/219
> > > generic/230
> > > generic/231
> > > generic/232
> > > generic/233
> > > generic/234
> > > generic/235
> > > generic/244
> > > generic/270
> > > generic/382
> > > 
> > > Would it be possible to handle this case and skip the test instead?
> > 
> > I'd like to ask a different question, which is there a reason to
> > support CONFIG_QFMT_V1 && !CONFIG_QFMT_V2?  Maybe we should just
> > always enable CONFIG_QFMT_V2, and simplify the test matrix?
> 
> Well, with ancient setups you could be using V1 quota format and then you
> don't need CONFIG_QFMT_V2. So I don't see a great reason to force enabling
> of CONFIG_QFMT_V2...
> 
> Omar's problem is actually that he had no quota format enabled so tools
> failed miserably to enable quotas although xfstests thought quota should be
> available. That could be viewed as a bug in _require_quota() macro in xfstests
> but OTOH userspace has no way of knowing which quota formats are available
> - it can only try to enable quota on a particular fs and that either fails
> or not. So implementing proper _require_quota() macro would mean you have
> to do full quota setup for some filesystem, try to enable quotas, and see if
> that fails. Doable but frankly I'm not hugely interested in that for such a
> cornercase...

Yeah, I'll just disable these tests. Thanks, Jan and Ted.

      parent reply	other threads:[~2018-01-18 18:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  1:09 ext4 quota tests fail with CONFIG_QFMT_V2=n Omar Sandoval
2018-01-18  1:28 ` Theodore Ts'o
2018-01-18  2:16   ` Omar Sandoval
2018-01-18  4:08     ` Theodore Ts'o
2018-01-18  8:17       ` Omar Sandoval
2018-01-18 12:08         ` Jan Kara
2018-01-18 23:26         ` Dave Chinner
2018-01-18 12:21   ` Jan Kara
2018-01-18 16:03     ` Theodore Ts'o
2018-01-19  8:46       ` Jan Kara
2018-01-19 17:14         ` Theodore Ts'o
2018-01-24 10:44           ` Jan Kara
2018-01-18 18:07     ` Omar Sandoval [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=20180118180728.GD10877@vader \
    --to=osandov@osandov.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --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