public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfstests: make sure $seq.full files don't land in /
Date: Wed, 14 Apr 2010 11:31:34 -0500	[thread overview]
Message-ID: <4BC5EDE6.7000001@sandeen.net> (raw)

186 and 192, at least, were landing (part of) their $seq.full
files in /

Fix this by using $here/$seq.full where needed.

Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---

diff --git a/186 b/186
index 94d399a..643f4b1 100755
--- a/186
+++ b/186
@@ -79,7 +79,7 @@ _rmv_eas()
 
 _filter_inode()
 {
-	tee -a $seq.full | \
+	tee -a $here/$seq.full | \
 		sed -e "s/core.forkoff/forkoff/g" | \
 		egrep '^u.sfdir2|^a.sfattr|forkoff' | \
 		egrep -v 'inumber|parent'
@@ -87,7 +87,7 @@ _filter_inode()
 
 _filter_version()
 {
-	tee -a $seq.full | tr ',' '\n' | grep ATTR
+	tee -a $here/$seq.full | tr ',' '\n' | grep ATTR
 }
 
 _print_inode()
diff --git a/192 b/192
index 0d0b294..d8301d5 100755
--- a/192
+++ b/192
@@ -68,7 +68,7 @@ time2=`_access_time $testfile | tee -a $seq.full`
 cd /
 umount $TEST_DIR
 _test_mount
-time3=`_access_time $testfile | tee -a $seq.full`
+time3=`_access_time $testfile | tee -a $here/$seq.full`
 
 delta1=`expr $time2 - $time1`
 delta2=`expr $time3 - $time1`


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-04-14 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 16:31 Eric Sandeen [this message]
2010-04-15 16:17 ` [PATCH] xfstests: make sure $seq.full files don't land in / Christoph Hellwig

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=4BC5EDE6.7000001@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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