From: Marco Benatto <mbenatto@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Eryu Guan <guaneryu@gmail.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 2/2] xfstests: Test root inode parent pointer repairing
Date: Fri, 22 Jun 2018 15:04:41 -0300 [thread overview]
Message-ID: <CAOGQQ2_cu66Dfw7J2Taj8jhN7-2Whdk24xFSD_5hrobe1sENvQ@mail.gmail.com> (raw)
In-Reply-To: <CAOGQQ2-_pgiPKPRoxHudZaoyAngd8+NW17oJDG+5N-e2R51m2g@mail.gmail.com>
Hello all,
just FYI just sent out v2 covering Dave's and Eryu's suggestions.
Thanks,
On Fri, Jun 22, 2018 at 12:17 PM, Marco Benatto <mbenatto@redhat.com> wrote:
> Hi Eryuy et al,
>
> firstly thanks for the reviews.
>
> OK, I'll resend just the test itself (without the one which hoist the
> helper function for sfdir format).
>
>
> Given Eric's and Dave's updates, should I re-include the common
> definitions even those being unused within
> this test scope?
>
> If those are used by helpers or any other flow on xfstest I do agree
> with Eric and Dave about hoist it.
>
> Thanks,
>
>
> On Fri, Jun 22, 2018 at 12:54 AM, Dave Chinner <david@fromorbit.com> wrote:
>> On Thu, Jun 21, 2018 at 09:58:25PM -0500, Eric Sandeen wrote:
>>> On 6/21/18 9:37 PM, Eryu Guan wrote:
>>> > On Mon, Jun 18, 2018 at 02:44:33PM -0300, Marco Benatto wrote:
>>> >> Recently we found out xfs_repair were not repairing
>>> >> root inode parent pointer when root inode is on short-form
>>> >> and parent points to an invalid inode number (refer to:
>>> >> "xfs_repair: Fix root inode's parent when it's bogus for sf
>>> >> directory" on xfs-devel list).
>>> >>
>>> >> This test checks if xfs_repair successfully repair the
>>> >> filesystem in the scenario mentioned before.
>>> >>
>>> >> Signed-off-by: Marco Benatto <mbenatto@redhat.com>
>>> >> ---
>>> >> tests/xfs/450 | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> >> tests/xfs/450.out | 1 +
>>> >> tests/xfs/group | 1 +
>>> >> 3 files changed, 55 insertions(+)
>>> >> create mode 100755 tests/xfs/450
>>> >> create mode 100644 tests/xfs/450.out
>>> >>
>>> >> diff --git a/tests/xfs/450 b/tests/xfs/450
>>> >> new file mode 100755
>>> >> index 0000000..dc7f244
>>> >> --- /dev/null
>>> >> +++ b/tests/xfs/450
>>> >> @@ -0,0 +1,53 @@
>>> >> +#! /bin/bash
>>> >> +# SPDX-License-Identifier: GPL-2.0
>>> >> +# Copyright (c) 2018 Red Hat Inc. All Rights Reserved.
>>> >> +#
>>> >> +# FS QA Test 450
>>> >> +#
>>> >> +# Make sure xfs_repair can repair root inode parent's pointer
>>> >> +# when it contains a bogus ino when it's using shot form directory
>>> >> +#
>>> >> +seq=`basename $0`
>>> >> +seqres=$RESULT_DIR/$seq
>>> >> +
>>> >> +status=1 # failure is the default!
>>> >
>>> > Apart from Dave's comments, there're some common definitions missing
>>> > too, e.g. 'tmp' and 'here', please use './new xfs' to generate new test
>>> > template.
>>>
>>> Eryu, I think I suggested that Marco could remove the "tmp" definition
>>> because it's not used in the script. Is there some reason to keep it?
>>> The script did start out with a "./new xfs" generation template.
>>>
>>> Oh, I bet some helpers depend on it... sorry, my mistake. Oops.
>>>
>>> (though maybe tmp should just get hoisted to the harness and
>>> not be required in every script, but I digress ...)
>>
>> You mean like I proposed a couple of weeks ago along with the
>> spdx license tag updates?
>>
>> https://www.spinics.net/lists/fstests/msg09849.html
>>
>> that's next on my list of "Big cleanups for fstests To Do" list.
>>
>> Cheers,
>>
>> Dave.
>> --
>> Dave Chinner
>> david@fromorbit.com
>
>
>
> --
> Marco Benatto
> Senior Software Maintenance Engineer | Red Hat Brasil
> T: +55 11 35246161 | M: +55 41 9 88504051
> Av. Brigadeiro Faria Lima 3900, 8° Andar. São Paulo, Brasil. RED HAT |
> TRIED. TESTED. TRUSTED. Saiba porque em redhat.com
--
Marco Benatto
Senior Software Maintenance Engineer | Red Hat Brasil
T: +55 11 35246161 | M: +55 41 9 88504051
Av. Brigadeiro Faria Lima 3900, 8° Andar. São Paulo, Brasil. RED HAT |
TRIED. TESTED. TRUSTED. Saiba porque em redhat.com
next prev parent reply other threads:[~2018-06-22 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 17:44 [PATCH 1/2] common/xfs: Add _scratch_get_sfdir_prefix function Marco Benatto
2018-06-18 17:44 ` [PATCH 2/2] xfstests: Test root inode parent pointer repairing Marco Benatto
2018-06-18 19:26 ` Darrick J. Wong
2018-06-20 1:48 ` Dave Chinner
2018-06-22 2:37 ` Eryu Guan
2018-06-22 2:58 ` Eric Sandeen
2018-06-22 3:54 ` Dave Chinner
2018-06-22 15:17 ` Marco Benatto
2018-06-22 18:04 ` Marco Benatto [this message]
2018-06-18 19:11 ` [PATCH 1/2] common/xfs: Add _scratch_get_sfdir_prefix function Darrick J. Wong
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=CAOGQQ2_cu66Dfw7J2Taj8jhN7-2Whdk24xFSD_5hrobe1sENvQ@mail.gmail.com \
--to=mbenatto@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).