public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/449: test xfs_info on a mounted block device
Date: Sat, 6 Jul 2019 08:35:57 -0700	[thread overview]
Message-ID: <20190706153557.GE5167@magnolia> (raw)
In-Reply-To: <20190706145217.13336-1-zlang@redhat.com>

On Sat, Jul 06, 2019 at 10:52:17PM +0800, Zorro Lang wrote:
> There was a bug, xfs_info fails on a mounted block device:
> 
>   # xfs_info /dev/mapper/testdev
>   xfs_info: /dev/mapper/testdev contains a mounted filesystem
> 
>   fatal error -- couldn't initialize XFS library
> 
>   xfsprogs has fixed it by:
> 
>     bbb43745 xfs_info: use findmnt to handle mounted block devices
> 
> Signed-off-by: Zorro Lang <zlang@redhat.com>

Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
>  tests/xfs/449 | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/xfs/449 b/tests/xfs/449
> index 6a031685..7aae1545 100755
> --- a/tests/xfs/449
> +++ b/tests/xfs/449
> @@ -60,10 +60,15 @@ echo GROWFS >> $seqres.full
>  cat $tmp.growfs >> $seqres.full
>  diff -u $tmp.mkfs $tmp.growfs
>  
> -$XFS_INFO_PROG $SCRATCH_MNT > $tmp.info
> -echo INFO >> $seqres.full
> -cat $tmp.info >> $seqres.full
> -diff -u $tmp.mkfs $tmp.info
> +$XFS_INFO_PROG $SCRATCH_MNT > $tmp.info.mnt
> +echo INFO_MNT >> $seqres.full
> +cat $tmp.info.mnt >> $seqres.full
> +diff -u $tmp.mkfs $tmp.info.mnt
> +
> +$XFS_INFO_PROG $SCRATCH_DEV > $tmp.info.dev
> +echo INFO_DEV >> $seqres.full
> +cat $tmp.info.dev >> $seqres.full
> +diff -u $tmp.mkfs $tmp.info.dev
>  
>  echo "Silence is golden."
>  status=0
> -- 
> 2.17.2
> 

      reply	other threads:[~2019-07-06 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06 14:52 [PATCH] xfs/449: test xfs_info on a mounted block device Zorro Lang
2019-07-06 15:35 ` Darrick J. Wong [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=20190706153557.GE5167@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@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