public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: xfs/322, verify xfs_quota administrator commands against invalid mount path
Date: Fri, 22 Nov 2013 17:12:46 +0800	[thread overview]
Message-ID: <528F200E.6060803@oracle.com> (raw)
In-Reply-To: <20131122085000.GD10132@dhcp-13-216.nay.redhat.com>

On 11/22 2013 16:50, Eryu Guan wrote:
> On Fri, Nov 22, 2013 at 03:53:38PM +0800, Jeff Liu wrote:
>> From: Jie Liu <jeff.liu@oracle.com>
>>
>> Introduce xfs/322 to verify xfs_quota administrator commands can
>> deal with invalid XFS mount path properly without NULL pointer
>> dereference issue.
>>
>> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
>> ---
>>  tests/xfs/322     | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  tests/xfs/322.out |  2 ++
>>  tests/xfs/group   |  1 +
>>  3 files changed, 71 insertions(+)
>>  create mode 100755 tests/xfs/322
>>  create mode 100644 tests/xfs/322.out
>>
>> diff --git a/tests/xfs/322 b/tests/xfs/322
>> new file mode 100755
>> index 0000000..9c749a1
>> --- /dev/null
>> +++ b/tests/xfs/322
>> @@ -0,0 +1,68 @@
>> +#! /bin/bash
>> +# FS QA Test No. 322
>> +#
>> +# Test to verify xfs_quota(8) administrator commands can deal with invalid
>> +# storage mount point without NULL pointer dereference problem.
>> +#
>> +#-----------------------------------------------------------------------
>> +# Copyright (c) 2013 Oracle Inc.  All Rights Reserved.
>> +#
>> +# This program is free software; you can redistribute it and/or
>> +# modify it under the terms of the GNU General Public License as
>> +# published by the Free Software Foundation.
>> +#
>> +# This program is distributed in the hope that it would be useful,
>> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
>> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>> +# GNU General Public License for more details.
>> +#
>> +# You should have received a copy of the GNU General Public License
>> +# along with this program; if not, write the Free Software Foundation,
>> +# Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
>> +#-----------------------------------------------------------------------
>> +#
>> +
>> +seq=`basename $0`
>> +seqres=$RESULT_DIR/$seq
>> +echo "QA output created by $seq"
>> +
>> +here=`pwd`
>> +tmp=/tmp/$$
>> +status=1	# failure is the default!
>> +trap "_cleanup; exit \$status" 0 1 2 3 15
>> +
>> +_cleanup()
>> +{
>> +    cd /
>> +    rm -f $tmp.*
>> +}
>> +
>> +# get standard environment, filters and checks
>> +. ./common/rc
>> +. ./common/filter
>> +
>> +# real QA test starts here
>> +
>> +# Modify as appropriate.
> 
> This comment is not needed.
> 
>> +_supported_fs generic
> 
> Should be "_supported_fs xfs" ?
Oops, exactly. Looks I have to refresh my head after completing a tedious task.

Thanks,
-Jeff

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-11-22  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  7:53 [PATCH] xfstests: xfs/322, verify xfs_quota administrator commands against invalid mount path Jeff Liu
2013-11-22  8:50 ` Eryu Guan
2013-11-22  9:12   ` Jeff Liu [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=528F200E.6060803@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=guaneryu@gmail.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