Re: [PATCH 2/7] tests: don't put loop control files on the scratch mount

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 2/7] tests: don't put loop control files on the scratch mount
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 26 May 2016 01:09:48 -0700
Cc: fstests@xxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <146424223512.6278.15231849939938178494.stgit@birch.djwong.org>
User-agent: Mutt/1.5.24 (2015-08-30)

Shouldn't these tests also add a _require_test now?  But we probably
should just move them to /tmp instead?

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

Follow-Ups:
- Re: [PATCH 2/7] tests: don't put loop control files on the scratch mount
  - From: Darrick J. Wong

References:
- [PATCH 0/7] xfstests: minor fixes for the reflink/dedupe tests
  - From: Darrick J. Wong
- [PATCH 2/7] tests: don't put loop control files on the scratch mount
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH 1/7] xfs/104: don't enospc when ag metadata overhead grows
Next by Date: Re: [PATCH 3/7] xfs: test copy-on-write leftover recovery
Previous by thread: [PATCH 2/7] tests: don't put loop control files on the scratch mount
Next by thread: Re: [PATCH 2/7] tests: don't put loop control files on the scratch mount
Index(es):
- Date
- Thread

[Index of Archives] [Linux XFS Devel] [Linux Filesystem Development] [Filesystem Testing] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux