All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/078: omit -m crc=0 mkfs option if mkfs.xfs has no meta support
Date: Wed, 22 Jul 2015 22:56:49 -0500	[thread overview]
Message-ID: <55B06601.2080204@sandeen.net> (raw)
In-Reply-To: <20150723035406.GG3945@dhcp-13-216.nay.redhat.com>

On 7/22/15 10:54 PM, Eryu Guan wrote:
> On Wed, Jul 22, 2015 at 10:22:56AM -0500, Eric Sandeen wrote:
>> On 7/22/15 3:22 AM, Eryu Guan wrote:
>>> This basically does the same as in commit
>>>
>>> 90a3bfc xfs: be compatible with older mkfs.xfs which has no v5 support
>>>
>>> which left xfs/078 behind.
>>>
>>> Signed-off-by: Eryu Guan <eguan@redhat.com>
>>
>> This is fine as far as it goes, but I think xfs/045 needs it too:
>>
>>
>> if ! _scratch_mkfs_xfs -m crc=0 >$tmp.out 2>&1
>> then
>>     cat $tmp.out
>>     echo "!!! failed to mkfs on $SCRATCH_DEV"
>>     exit
>> fi
>>
>> It fails "gracefully" but it doesn't need to, in this case.
> 
> xfs/045 passed on my RHEL6 test box, I think that's because xfs/045 (and
> some other tests) takes use of _scratch_mkfs_xfs not call $MKFS_XFS_PROG
> directly, so commit 90a3bfc takes care of all the dirty work.
> 
> Thanks for the review!

Oh, you are right ... how did I miss that it's calling _scratch_mkfs_xfs,
I'm sorry!

Yes, your patch is fine, and complete.  Oops! :)

Thanks,
-Eric

      reply	other threads:[~2015-07-23  3:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22  8:22 [PATCH] xfs/078: omit -m crc=0 mkfs option if mkfs.xfs has no meta support Eryu Guan
2015-07-22 15:22 ` Eric Sandeen
2015-07-23  3:54   ` Eryu Guan
2015-07-23  3:56     ` Eric Sandeen [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=55B06601.2080204@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.