xfs
[Top] [All Lists]

Re: [PATCH 7/9] xfstests: add a new quota test that runs fsstress under

To: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
Subject: Re: [PATCH 7/9] xfstests: add a new quota test that runs fsstress under ENOSPC conditions
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 3 Nov 2011 15:39:35 -0400
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, aelder@xxxxxxx, tytso@xxxxxxx, hch@xxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <1320342953-7973-7-git-send-email-dmonakhov@xxxxxxxxxx>
References: <1320342953-7973-1-git-send-email-dmonakhov@xxxxxxxxxx> <1320342953-7973-7-git-send-email-dmonakhov@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Nov 03, 2011 at 09:55:51PM +0400, Dmitry Monakhov wrote:
> - Same as 264 but with quota enabled.

269 is the new 270

> - IO performed from $qa_user user
> - fsstress granted with CAP_CHOWN capability.

This fails in my test VM because it doesn't have setcap.  If you
want to use additional non-standard tools please do a _notrun if
they aren't present.

I don't quite understand why it would need CAP_CHOWN - chowns
from owned files do not require it, and the test runs fine with
the setcap line commented out.

I'll commit it as-is for now, but unless I get some feedback on
why the setcap is require I'll add another commit to remove it ASAP.

<Prev in Thread] Current Thread [Next in Thread>