From: Christoph Hellwig <hch@infradead.org>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH v2 0/3] xfs: fix quota related problems
Date: Thu, 28 Nov 2013 02:41:15 -0800 [thread overview]
Message-ID: <20131128104115.GD26927@infradead.org> (raw)
In-Reply-To: <5294A449.9010202@oracle.com>
On Tue, Nov 26, 2013 at 09:38:17PM +0800, Jeff Liu wrote:
> Since the infinite loop and assertion issue are failed due to different issues, I
> wonder if we'd better to add two test cases to cover them separately or not? i.e,
> One sanity check to verify turning group/project off quota with user quota is active,
> another test to verify turning group/project quota off with fsstress is running.
I always prefer to have isolated cases for bugs that are trivially
reprodible instead of relying on heavy stress tests with multiple
components. Vote for two test cases from me!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-11-28 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:38 [PATCH v2 0/3] xfs: fix quota related problems Jeff Liu
2013-11-28 10:41 ` Christoph Hellwig [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=20131128104115.GD26927@infradead.org \
--to=hch@infradead.org \
--cc=jeff.liu@oracle.com \
--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