public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common/rc: use $FSTYP and $SCRATCH_DEV in _supports_filetype function
Date: Mon, 16 Jan 2017 16:04:05 +0800	[thread overview]
Message-ID: <587C7E75.80008@cn.fujitsu.com> (raw)
In-Reply-To: <20170116072352.GE1859@eguan.usersys.redhat.com>

On 2017/01/16 15:23, Eryu Guan wrote:
> On Mon, Jan 16, 2017 at 02:40:19PM +0800, Xiao Yang wrote:
>> generic/401 failed on RHEL6.8GA because output option is not
>> supported by df.  So we use $FSTYP and $SCRATCH_DEV instead of
>> df --output to fix it.
>>
>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
>> ---
>>   common/rc | 6 ++----
>>   1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/common/rc b/common/rc
>> index 892c46e..90ad496 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -268,14 +268,12 @@ _supports_filetype()
>>   {
>>   	local dir=$1
>>
>> -	local fstyp=$(df --output=fstype $dir | tail -1)
>> -	case "$fstyp" in
>> +	case $FSTYP in
> $FSTYP can't be used directly in this function, because it's also used
> to detect the fstype of upperfs of overlayfs in overlay testing, in
> which case FSTYP is overlay. See _overlay_mount().
>
> Just remove "--output=xxx" option and parse the output, e.g.
>
> local fstyp=`$DF_PROG $dir | tail -1 | $AWK_PROG '{print $2}'`
>
> Note that $DF_PROG is defined as "df -T -P", which prints the fstyp
> field.
>
>
Hi Eryu

Thanks for your explanations, i will rewrite this patch.

Best Regards,
Xiao Yang

>>   	xfs)
>>   		xfs_info $dir | grep -q "ftype=1"
>>   		;;
>>   	ext2|ext3|ext4)
>> -		tune2fs -l $(df --output=source $dir | tail -1) | \
>> -		   grep -q filetype
>> +		tune2fs -l $SCRATCH_DEV | grep -q filetype
> Same here, $SCRATCH_DEV doesn't fit.
>
> Thanks,
> Eryu
>
>>   		;;
>>   	*)
>>   		local testfile=$dir/$$.ftype
>> -- 
>> 1.8.3.1
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fstests" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> .
>




  reply	other threads:[~2017-01-16  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  6:40 [PATCH] common/rc: use $FSTYP and $SCRATCH_DEV in _supports_filetype function Xiao Yang
2017-01-16  7:23 ` Eryu Guan
2017-01-16  8:04   ` Xiao Yang [this message]
2017-01-16  8:07   ` [PATCH v2] common/rc: Fix " Xiao Yang
2017-01-16  8:20     ` Eryu Guan
2017-01-16  8:24       ` Xiao Yang

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=587C7E75.80008@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox