From: Lachlan McIlroy <lmcilroy@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: 220 - generic quota sanity
Date: Mon, 10 Aug 2009 21:59:45 -0400 (EDT) [thread overview]
Message-ID: <669295477.1736351249955985378.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <20090810160949.GA21948@infradead.org>
----- "Christoph Hellwig" <hch@infradead.org> wrote:
> On Mon, Aug 10, 2009 at 09:05:17AM -0500, Eric Sandeen wrote:
> > Lachlan McIlroy wrote:
> > > This looks good Eric.
> > >
> > > Is this test just for quota accounting or should it be testing
> quota
> > > enforcement too?
> >
> > I guess 108 just did accounting; I was going to keep it parallel,
> and do
> > a different one for accounting, but it could be added to this as
> well.
>
> Yeah, let's use a different one for enforement testing.
Agree, if quota enforcement isn't working correctly then the accounting
is the first thing to check so having seperate tests is a good idea.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-11 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 19:10 [PATCH] xfstests: 220 - generic quota sanity Eric Sandeen
2009-08-10 5:13 ` Lachlan McIlroy
2009-08-10 14:05 ` Eric Sandeen
2009-08-10 16:09 ` Christoph Hellwig
2009-08-11 1:59 ` Lachlan McIlroy [this message]
2009-08-10 14:38 ` [PATCH V2 1/2] xfstests: split out xfs & generic quota existence tests Eric Sandeen
2009-08-10 15:44 ` Christoph Hellwig
2009-08-10 14:40 ` [PATCH V2 2/2] xfstests: 220 - generic quota sanity Eric Sandeen
2009-08-10 16:09 ` Christoph Hellwig
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=669295477.1736351249955985378.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=lmcilroy@redhat.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--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