branches: 1.17.2;
bsd.own.mk: rename GCC_NO_* to CC_WNO_*

Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.

GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.

remove GCC_NO_ADDR_OF_PACKED_MEMBER for several subdir builds
that are now handled by lfs_accessors.h internally.

avoid new GCC 9 warnings.

LIBISPRIVATE=yes

introduce some common variables for use in GCC warning disables:

GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8)
GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8)
GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8)
GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8)

use these to turn off warnings for most GCC-8 complaints. many
of these are false positives, most of the real bugs are already
commited, or are yet to come.


we plan to introduce versions of (some?) of these that use the
"-Wno-error=" form, which still displays the warnings but does
not make it an error, and all of the above will be re-considered
as either being "fix me" (warning still displayed) or "warning
is wrong."

branches: 1.12.26;
Make the abs() use check non-fatal for a bogus use in the LFS cleanerd.

Add UDF as one of the filesytems to test. Might help understand why rump is
misbehaving on it.

Highly uncool to stash a partial copy of the ti-rpc code here.

branches: 1.9.2;
Hook ZFS tests to MKZFS instead of a homegrown variable.

Add a vfstest zfs attachment. This is a compile-time option,
default off, due the large numbers of failing tests (some of them
look like quite trivial failures).

branches: 1.7.2;
add ATF tests for v7fs. patch by njoly@. thank you.

Add rumpfs to list of file systems to be autotested.

.PARSEDIR doesn't work. at least not for me. Use .CURDIR instead
which makes a build with objdir succeed.

Include & use lfs megamaid.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Add NFS to the list of file systems exercised by the "vfs" tests.

How it works:
NFS tests fork and exec the nfs service from fs/nfs/nfsservice.
The child then:
a) creates a FFS file system
b) mounts it
c) starts rpcbind
d) starts mountd
e) starts nfsd
f) handles requests

The client, as expected, does the standard RPC regotiation and
calls mount(MOUNT_NFS). It then proceeds to execute the test.

An individual test which executes everything described above and
does a few file operations on the NFS mount takes 0.16s wall time
on my laptop from start to finish. This means it is feasible to
run hundreds of tests while still getting results in a timely
fashion.

Like in other networked tests, the two processes are connected via
the rump shmif which uses mmapped files as ethernet busses. The
entire test suite can be executed by an unprivileged account.

As a side effect, these tests exercise also the kernel NFS server
in addition to the kernel NFS client.

While everything is currently targetted at executing the vfs tests,
there is no reason this could not be extended to exercise features
specific to NFS. For example, the server can run through all
exportable file system types, permissions can be tested, etc.

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.

branches: 1.1.2;
file fstest_exfatfs.c was initially added on branch perseant-exfatfs.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Fix ffs_fstest_delfs's error branch for rump_pub_etfs_remove.

rump_pub_etfs_remove returns an error code, rather than setting errno
and returning -1.

branches: 1.5.2;
ggr, how many of those I will need to fix. Fallout from the bogus inclusion
of <signal.h> in rump_syscallargs.h.

wrap system() in SIG_DFL so that child-bearing fs tests (puffs,
nfs) don't go cuckoo when the process executed by system() takes a
backstage left.

add another fstype for ffs -o log

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Add in-kernel cleaner. Move cleaning-related routines into their own file.
Document the fcntl calls better in lfs.h. Bounds-check inode numbers in
segment parsing functions. Use the in-kernel cleaner in a greedy mode
for tests in tests/fs/vfs, and add a test of the kernel cleaner.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

The cleaner is compiled into the ATF test harness for the LFS
filesystem tests. Use the new -J option to pass the raw device into
the cleaner. This avoids the not rump safe getdiskrawname call and
makes sure we use an internal rump device name for cleaning. This
should fix bin/54488.

branches: 1.6.2;
Call rump_pub_lwproc_newlwp() in the lfs cleaner thread to make its
rump system calls all use the same lwp. Hopefully this will fix
PR kern/53884. Also call rump_pub_lwproc_releaselwp() at the end.

branches: 1.5.14; 1.5.16;
Remove rubbish.

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

whitespace

Include & use lfs megamaid.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Initialise permissions mask to a sensible value (0755).
While here convert leading spaces to tabs.

branches: 1.2.6;
Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

fix a/an grammar in obvious cases

branches: 1.12.8;
Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

sprintf->snprintf

don't check the return value of execvp() for failure to call err().
assume if it returns at all something has failed.

branches: 1.9.44;
g/c use of unused variable too

g/c unused variable

bump nfdsargv[]�size belatedly (and add a few extra for needs of future bugs)

Do initialise allocated file system args structures for puffs and nfs
(fix some puffs tests failures with MALLOC_OPTIONS=J).
While here, detect and report args allocation failure.

ok from pooka.

branches: 1.5.2;
Configure two network addresses for the nfs server. One exports
/myexport r/w to the client in the same subnet and the other one
exports /myexport r/o to the client in the same subnet.

Put the workaround for PR kern/43799 into the common nfs unmount routine.

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Wait for child (rumpnfsd) to die before declaring unmount successful.
(yes, should be in delfs, but delfs doesn't work due to the cleanup hassle)

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

fix typos in comments and one definition, mainly s/sucket/socket/.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

don't check the return value of execvp() for failure to call err().
assume if it returns at all something has failed.

branches: 1.11.26;
Remove what looks like an outdated assert (there was something very sneaky
about this code, but my memory is fading ...)

branches: 1.10.4; 1.10.10;
Do initialise allocated file system args structures for puffs and nfs
(fix some puffs tests failures with MALLOC_OPTIONS=J).
While here, detect and report args allocation failure.

ok from pooka.

branches: 1.9.2;
Don't panic if "unnecessary" dir already exists.
(helpful when running the test without atf-run)

Add a puffs-p2k-ffs file system type to automated tests. Inspired
by the file handle problem in p2k.

don't assume atomic read/write on socketpair. puffs_kargs at least is
too large to assume atomic read/write. this makes some tests including
fs/puffs/t_basic pass on my environment.

Make the shovel threads resilient to file server exit.

Fix format strings so it builds on amd64

Since rump implicit threads now bind to proc1 instead of proc0, we
need our shovel threads bound to proc1 instead of proc0 in order
to have access to the same set of descriptors as the implicit thread
which opens the fd in the rump kernel.

Also, sprinkle some printfs and make failure more dramatic.

fixes the puffs tests. pointed out by pgoyette.

update to new rump lwp/proc interfaces

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Retrict rumpfs to the provided size, like other filesystems.

branches: 1.1.6; 1.1.12;
Add rumpfs to list of file systems to be autotested.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

branches: 1.4.6; 1.4.10;
Use the new extension to newfs_udf to generate a decent image for rump to work
on instead of an FFS(!) version.

Initialize mount args version info.
Add comment about a bogusly used "newfs" where "newfs_udf" is meant.

Fix copy & pasto, notice by Nicolas Joly, one step closer to solving
PR kern/47974.

Add UDF as one of the filesytems to test. Might help understand why rump is
misbehaving on it.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

add ATF tests for v7fs. patch by njoly@. thank you.

Include explicitly <rump/rump_syscallshotgun.h> for previous indirect users
via <rump/rump.h>.

Have to hijack sysctl() and modctl() for zfs commands.

Should fix PR kern/53422

branches: 1.1.4; 1.1.32; 1.1.34;
Add a vfstest zfs attachment. This is a compile-time option,
default off, due the large numbers of failing tests (some of them
look like quite trivial failures).

Rework the optional building of ZFS tests to make it easier to add other
optional filesystems in future. Verified to produce identical binaries.

branches: 1.44.8;
Skip tests when we know there is not enough space available

Hardcode a check for ZFS and too little free space in workdir to skip
ZFS tests if the atf working directory is size restricted (ZFS has a
hardcoded minimal size of 64MB for a storage pool and 128 MB disk size).

branches: 1.42.2;
No semicolon after macro do ... while (0) wrapper.

branches: 1.41.12;
Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.40.2;
Fix glaringly wrong indent.

zfs tests don't actually need privileges.

Add UDF as one of the filesytems to test. Might help understand why rump is
misbehaving on it.

Mark the zfs tests as requiring root.

This is wrong. The zfs tests already use rump so they should not require
root. However, I've already spent much more time than I wanted trying to
figure out why that's the case without much luck. If you can find why,
just remove this hack.

branches: 1.36.2;
Add a vfstest zfs attachment. This is a compile-time option,
default off, due the large numbers of failing tests (some of them
look like quite trivial failures).

branches: 1.35.2;
add ATF tests for v7fs. patch by njoly@. thank you.

Remove unnecessary (and broken) cleanup routines.

The cleanup routines were being used to kill the rump process and to delete
the temporary image file. These are things automatically done by atf-run,
but it looks like this code was added here to workaround a previous bug in
the atf-run code.

Note that, in the existing form, the cleanup routines segfault (haven't
spent the time to track down why). atf-run does not care about this
(although it should), buy Kyua does.

As a side effect, this has a teeny-tiny performance speedup in the execution
of the tests including this file.

OKed by njoly@.

Put p2k_ffs back there -- i can't repeat any problems in my qemu/anita
runs.

Apparently the atf in the qemu runs doesn't like p2k_ffs and hangs
completely. Remove it for until I have a chance to debug what's
going on.

Adjust atf_check_type() to make it work again.
Do we need tests for the tests? ;)

Set an extra xvar indicating MOUNT_FOO

antipasto

add another fstype for ffs -o log

adjust another place where X-fs.type is set

Use our internal name instead of MOUNT_FOO to identify file system
since otherwise we now run into dupes (e.g. nfs and nfsro, puffs
and p2k_ffs).

Add a puffs-p2k-ffs file system type to automated tests. Inspired
by the file handle problem in p2k.

Introduce r/o tests. They do two mounts: the first one is r/w and
runs a generator which primes the fs. The second one is r/o and
does the actual testing. Also, introduce a nfsro fstype which does
a clientside r/w mount for a r/o server export.

requested by yamt

(one nfsro test currently fails with EROFS vs. EACCES. Hopefully
someone else can debate the correct errno)

Sprinkle some KNF. No functional change.

Add rumpfs to list of file systems to be autotested.

Adjusts tests after import of atf-0.12:

- The use.fs property is gone.
- Mark the tests/fs/t_create:attrs test as broken when using the default
unprivileged-user:_atf setting. This probably deserves a fix somehow
but I'm not sure at this point.

include some necessary headers to fix build

* fail with errnos
* in case unmount fails, call rump_pub_vfs_mount_print() to print
mountpoint status and dump active vnodes.

allow overriding of defaults

Fold the puffs private and vfs tests mount/unmount routines together.
To achieve this, add a file system private parameter to the newfs
method (which will obviously not be used by vfs tests).

njoly ok

Move nfstestargs to header "because I need them". A more sweeping
action would be good here.

Add FSTEST_CONSTRUCTOR/FSTEST_DESTRUCTOR which create/mount the
file system with default params. Make ATF_FS_APPLY use the
constructor (can't use the destructor due to the (useless) cleanup).

Add NFS to the list of file systems exercised by the "vfs" tests.

How it works:
NFS tests fork and exec the nfs service from fs/nfs/nfsservice.
The child then:
a) creates a FFS file system
b) mounts it
c) starts rpcbind
d) starts mountd
e) starts nfsd
f) handles requests

The client, as expected, does the standard RPC regotiation and
calls mount(MOUNT_NFS). It then proceeds to execute the test.

An individual test which executes everything described above and
does a few file operations on the NFS mount takes 0.16s wall time
on my laptop from start to finish. This means it is feasible to
run hundreds of tests while still getting results in a timely
fashion.

Like in other networked tests, the two processes are connected via
the rump shmif which uses mmapped files as ethernet busses. The
entire test suite can be executed by an unprivileged account.

As a side effect, these tests exercise also the kernel NFS server
in addition to the kernel NFS client.

While everything is currently targetted at executing the vfs tests,
there is no reason this could not be extended to exercise features
specific to NFS. For example, the server can run through all
exportable file system types, permissions can be tested, etc.

Update ATF_TC_FSADD macro use ATF cleanup function. And call
xx_fstest_delfs() from here instead of test body.

* namespace some macros under FSTEST
* inline atf_check_tc() since this is a header

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Run puffs/dtfs as part of the vfs tests.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Make the FSTYPE macros take tc instead of derivative type "type".

ok njoly

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Pass down the test case data to the test function, to be able to use
meta-data informations such as srcdir. Requested by pooka.

While here remove fstype argument, and define it as a custom meta-data
(X-fs.type) instead.

Get rid of home made filesystem type strings and use MOUNT_xxx ones
instead. While here provide some macros which do test for a specific
type.

Pass down the filesystem type to the test funtion to allow fs-specific
callpoints.

Adjust t_rmdirrace by moving LFS test specific code from common/lfs.c,
and do skip sysvbfs which does not support rmdir(2).

from pooka.

Add LFS to vfs test list. TODO: start cleanerd too.

It fails in a number of different ways. Some of them seem to appear
as a function of the file system size (i'm not sure if it's because
the lack of the cleaner or not. i'm guessing ``no'', though).

ok njoly

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Remove the lfs race condition hack now that it's properly in the
test instead of the fs-specific part.

Pass down the filesystem type to the test funtion to allow fs-specific
callpoints.

Adjust t_rmdirrace by moving LFS test specific code from common/lfs.c,
and do skip sysvbfs which does not support rmdir(2).

from pooka.

fill in PR number now that we have one

Add LFS to vfs test list. TODO: start cleanerd too.

It fails in a number of different ways. Some of them seem to appear
as a function of the file system size (i'm not sure if it's because
the lack of the cleaner or not. i'm guessing ``no'', though).

ok njoly

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Move nfstestargs to header "because I need them". A more sweeping
action would be good here.

Add NFS to the list of file systems exercised by the "vfs" tests.

How it works:
NFS tests fork and exec the nfs service from fs/nfs/nfsservice.
The child then:
a) creates a FFS file system
b) mounts it
c) starts rpcbind
d) starts mountd
e) starts nfsd
f) handles requests

The client, as expected, does the standard RPC regotiation and
calls mount(MOUNT_NFS). It then proceeds to execute the test.

An individual test which executes everything described above and
does a few file operations on the NFS mount takes 0.16s wall time
on my laptop from start to finish. This means it is feasible to
run hundreds of tests while still getting results in a timely
fashion.

Like in other networked tests, the two processes are connected via
the rump shmif which uses mmapped files as ethernet busses. The
entire test suite can be executed by an unprivileged account.

As a side effect, these tests exercise also the kernel NFS server
in addition to the kernel NFS client.

While everything is currently targetted at executing the vfs tests,
there is no reason this could not be extended to exercise features
specific to NFS. For example, the server can run through all
exportable file system types, permissions can be tested, etc.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

catch "child died"

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

off_t -> uint64_t to hopefully avoid some lp64 signedness whines.

Run puffs/dtfs as part of the vfs tests.

return return atf_no_error() instead of 0 for consistency.

suggested by moritzbuhl in https://github.com/NetBSD/src/pull/11/

branches: 1.7.30;
Test taking a snapshot from a stressed file system.
Checks snapshot meta data only with fsck.

OK: Antti Kantee <pooka@netbsd.org>

branches: 1.6.4; 1.6.10;
Test the right fd after rump_sys_open().

branches: 1.5.2;
Adjusts tests after import of atf-0.12:

- The use.fs property is gone.
- Mark the tests/fs/t_create:attrs test as broken when using the default
unprivileged-user:_atf setting. This probably deserves a fix somehow
but I'm not sure at this point.

atf-0.9 introduces an use.fs test-case property to allow tests to write to
their work directory. The purpose is to be able to know which tests intend
to touch the file system and to allow a minor optimization in atf-run.

Define use.fs=true for all those tests requiring it. (This highlights that
some tests currently require modifying the file system but conceptually
they shouldn't be... which leaves room for further improvements/cleanups
later :-)

Now that atf gdb/coredump conflicts have been solved (thanks jmmv!),
remove USE_ATF ifdefs.

Add the typical #ifdef USE_ATF stuff so I can debug the test if it
goes wrong.

Split snapshot test into fs-independent backend and fs-specific frontend.

I really wish all our fs tests were like this (in principle, that
is. I'm not talking about this hacky implementation). I've been
wishing this for quite a few years now. Seems like my wishes don't
come true.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.

Rename xfs.c to fstest_xfs.c to avoid collisions with other
source files with the name xfs.c

ok njoly

Convert the file system test common routines into a library to
facilitate more complex user-side stuff (like the lfs cleaner and
nfs rpc code), which are non-trivial to do by #include.

Add testcase data argument to all fstest helper functions.
Needed by pooka for puffs fstest support.

Update filesystem helper functions namespace (from XXX_mount to
XXX_fstest_mount) to avoid conflicts with existing functions such as
puffs_mount.

Fix more copyrights, where i forgot to add my name.

Add helper code and macros to ease writing filesystem tests with rump.
Support currently limited to ext2fs, ffs, msdos, sysvbfs and tmpfs.