All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Omar Sandoval <osandov@osandov.com>
Cc: fstests@vger.kernel.org, Jan Kara <jack@suse.cz>,
	Eryu Guan <eguan@redhat.com>
Subject: Re: ext4 quota tests fail with CONFIG_QFMT_V2=n
Date: Wed, 17 Jan 2018 20:28:31 -0500	[thread overview]
Message-ID: <20180118012831.GF6948@thunk.org> (raw)
In-Reply-To: <20180118010936.GA10649@vader>

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?

       	      		      	  	       	    - Ted

  reply	other threads:[~2018-01-18  1:28 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 [this message]
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

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=20180118012831.GF6948@thunk.org \
    --to=tytso@mit.edu \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=osandov@osandov.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.