All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Cc: eguan@redhat.com, fstests@vger.kernel.org, dedekind1@gmail.com,
	richard.weinberger@gmail.com, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/5] xfstest: add ubifs support
Date: Mon, 3 Aug 2015 15:51:49 +1000	[thread overview]
Message-ID: <20150803055149.GR3902@dastard> (raw)
In-Reply-To: <55BEF1A3.9060103@cn.fujitsu.com>

On Mon, Aug 03, 2015 at 12:44:19PM +0800, Dongsheng Yang wrote:
> On 08/03/2015 12:12 PM, Dave Chinner wrote:
> >On Thu, Jul 30, 2015 at 02:06:53PM +0800, Dongsheng Yang wrote:
> >>-	echo $TEST_DEV | grep -qE ":|//" > /dev/null 2>&1
> >>+	echo $TEST_DEV | grep -qE ":|//|ubi" > /dev/null 2>&1
> >>  	if [ ! -b "$TEST_DEV" -a "$?" != "0" ]; then
> >>-		echo "common/config: Error: \$TEST_DEV ($TEST_DEV) is not a block device or a network filesystem"
> >>+		echo "common/config: Error: \$TEST_DEV ($TEST_DEV) is not a block device or a network filesystem or ubi device"
> >>  		exit 1
> >>  	fi
> >>
> >>@@ -488,9 +489,9 @@ get_next_config() {
> >>  		export SCRATCH_DEV_NOT_SET=true
> >>  	fi
> >>
> >>-	echo $SCRATCH_DEV | grep -qE ":|//" > /dev/null 2>&1
> >>+	echo $SCRATCH_DEV | grep -qE ":|//|ubi" > /dev/null 2>&1
> >>  	if [ ! -z "$SCRATCH_DEV" -a ! -b "$SCRATCH_DEV" -a "$?" != "0" ]; then
> >>-		echo "common/config: Error: \$SCRATCH_DEV ($SCRATCH_DEV) is not a block device or a network filesystem"
> >>+		echo "common/config: Error: \$SCRATCH_DEV ($SCRATCH_DEV) is not a block device or a network filesystem or ubi device"
> >>  		exit 1
> >>  	fi
> >
> >Hmmm - how do we validate that we were passed a valid ubi device in
> >TEST_DEV/SCRATCH_DEV? (goes back to the probing question above...)
> 
> I am using the following config for my testing. So if we want to
> test ubifs, we have to pass a ubi volume to it. the name of it
> looks as ubiX_X.
> 
> # cat local.config
> # Ideally define at least these 4 to match your environment
> # The first 2 are required.
> # See README for other variables which can be set.
> #
> # Note: SCRATCH_DEV >will< get overwritten!
> 
> export TEST_DEV=/dev/ubi0_0
> export TEST_DIR=/mnt/test
> export SCRATCH_DEV=/dev/ubi0_1
> export SCRATCH_MNT=/mnt/scratch

So if we see /dev/ubi???? then we should check that it's a char
device to confirm it is what we think it should be?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2015-08-03  5:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30  6:06 [PATCH 0/5] xfstests: introduce ubifs in xfstests Dongsheng Yang
2015-07-30  6:06 ` Dongsheng Yang
2015-07-30  6:06 ` [PATCH 1/5] xfstest: add ubifs support Dongsheng Yang
2015-07-30  6:06   ` Dongsheng Yang
2015-08-03  4:12   ` Dave Chinner
2015-08-03  4:44     ` Dongsheng Yang
2015-08-03  4:44       ` Dongsheng Yang
2015-08-03  4:47       ` Dongsheng Yang
2015-08-03  4:47         ` Dongsheng Yang
2015-08-03  5:51       ` Dave Chinner [this message]
2015-07-30  6:06 ` [PATCH 2/5] xfstest: generic/219 add _require_odirect Dongsheng Yang
2015-07-30  6:06   ` Dongsheng Yang
2015-08-03  3:11   ` Eryu Guan
2015-08-03  3:59   ` Dave Chinner
2015-08-03  5:01     ` Dongsheng Yang
2015-08-03  5:01       ` Dongsheng Yang
2015-08-03  5:55       ` Dave Chinner
2015-07-30  6:06 ` [PATCH 3/5] xfstest: generic/125 " Dongsheng Yang
2015-07-30  6:06   ` Dongsheng Yang
2015-08-03  3:12   ` Eryu Guan
2015-07-30  6:06 ` [PATCH 4/5] xfstest: introduce subtestset for ubifs Dongsheng Yang
2015-07-30  6:06   ` Dongsheng Yang
2015-08-03  3:28   ` Eryu Guan
2015-08-03  5:12     ` Dongsheng Yang
2015-08-03  5:12       ` Dongsheng Yang
2015-07-30  6:06 ` [PATCH 5/5] xfstest: add quota tests to ubifs Dongsheng Yang
2015-07-30  6:06   ` Dongsheng 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=20150803055149.GR3902@dastard \
    --to=david@fromorbit.com \
    --cc=dedekind1@gmail.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    --cc=yangds.fnst@cn.fujitsu.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 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.