summaryrefslogtreecommitdiffstats
path: root/tools/regression
Commit message (Collapse)AuthorAgeFilesLines
* Add explicit casting in few places.pjd2009-02-231-12/+12
| | | | | | | | | It is only really necessary for open(2)'s third argument, which is optional and obtained through stdarg(3). open(2)'s third argument is 32bit and we pass 64 bits. On little endian it works, because we take lower 32 bits, but on big endian platforms we take upper 32 bits, so we end up with 0. Reported by: Milan Čermák <Milan.Cermak@Sun.COM>
* Add a regresion test to determine whether or not a file descriptor isrwatson2009-02-112-0/+129
| | | | | | | | | | | | | | | | | allocated in a fork(2)-inheritable way at the beginning or end of an accept(2) system call. This test creates a test thread and blocks it in accept(2), then forks a child process which tests to see if the next available file descriptor is defined or not (EBADF vs EINVAL for ftruncate(2)). This detects a regression introduced during the network stack locking work, in which a very narrow race during which fork(2) from one thread during accept(2) in a second thread lead to an extra inherited file descriptor turned into a very wide race ensuring that a descriptor was leaked into the child even though it hadn't been returned. PR: kern/130348
* Test wprintf() in addition to printf().das2009-01-311-3/+19
|
* Add tests for conj{,f,l}() that I wrote some time ago. These test thedas2009-01-313-1/+169
| | | | versions in libm, not the gcc builtins.
* Be more Solaris-friendly.pjd2009-01-162-4/+8
| | | | Submitted by: Milan Cermak <Milan.Cermak@Sun.COM>
* Allow jot(1) regression tests to be checked out on Windows filesystems.ed2009-01-162-1/+1
| | | | | | | | The jot(1) regression tests directory contained two tests named `wx' and `wX', which doesn't work on case insensitive filesystems. Rename `wX' to `wX1'. MFC after: 1 month
* Update for 185401, errors now go to stderr.stefanf2008-11-281-0/+0
|
* Add tools-level test for POSIX.1e functionality.trasz2008-11-253-0/+632
| | | | Approved by: rwatson (mentor)
* This actually works on Linux, I just had wrong directory permission.pjd2008-11-241-4/+0
| | | | Found by: trasz
* Include TODO messages even if tests succeeds, so we can detect when somethingpjd2008-11-241-6/+18
| | | | suddenly started to work.
* Add a test for r185231.stefanf2008-11-231-0/+9
|
* Mark all the places where Linux is not POSIX-compilant. Tested on ext3.pjd2008-11-233-0/+8
|
* fstest for Linux:pjd2008-11-239-56/+53
| | | | | | | - Use -- when needed so Linux getopt(3) won't get confused. - Follow POSIX more closely. Submitted by: Szabolcs Szakacsits <szaka@ntfs-3g.org>
* fstest for Linux:pjd2008-11-231-2/+26
| | | | Automatically detect file system type.
* FreeBSD's way of handling rmdir("..") is not POSIX-compilant.pjd2008-11-231-9/+3
|
* Shorter version.pjd2008-11-231-14/+4
|
* Add support for pathconf(2).pjd2008-11-231-1/+57
|
* Detect operating system automatically.pjd2008-11-231-5/+21
|
* fstest for Linux:pjd2008-11-231-4/+27
| | | | | - Use /dev/urandom, it is more portable. - Implement todo() function which allows to mark known failures.
* IFp4: Regression tests for FreeBSD/ZFS chflags(2)/lchflags(2).pjd2008-11-2214-88/+136
|
* Update ZFS from version 6 to 13 and bring some FreeBSD-specific changes.pjd2008-11-1754-0/+12014
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bring huge amount of changes, I'll enumerate only user-visible changes: - Delegated Administration Allows regular users to perform ZFS operations, like file system creation, snapshot creation, etc. - L2ARC Level 2 cache for ZFS - allows to use additional disks for cache. Huge performance improvements mostly for random read of mostly static content. - slog Allow to use additional disks for ZFS Intent Log to speed up operations like fsync(2). - vfs.zfs.super_owner Allows regular users to perform privileged operations on files stored on ZFS file systems owned by him. Very careful with this one. - chflags(2) Not all the flags are supported. This still needs work. - ZFSBoot Support to boot off of ZFS pool. Not finished, AFAIK. Submitted by: dfr - Snapshot properties - New failure modes Before if write requested failed, system paniced. Now one can select from one of three failure modes: - panic - panic on write error - wait - wait for disk to reappear - continue - serve read requests if possible, block write requests - Refquota, refreservation properties Just quota and reservation properties, but don't count space consumed by children file systems, clones and snapshots. - Sparse volumes ZVOLs that don't reserve space in the pool. - External attributes Compatible with extattr(2). - NFSv4-ACLs Not sure about the status, might not be complete yet. Submitted by: trasz - Creation-time properties - Regression tests for zpool(8) command. Obtained from: OpenSolaris
* Add a test for the "or more" part of the following POSIX specification.dds2008-11-112-1/+3
| | | | | | "A function can be preceded by one or more '!' characters, in which case the function shall be applied if the addresses do not select the pattern space."
* Make test for write access to the directory being moved a little moretrasz2008-11-071-5/+9
| | | | | | specific. Approved by: rwatson (mentor)
* Improve output when a test fails.trasz2008-11-071-2/+2
| | | | Approved by: rwatson (mentor)
* Change ZFS behaviour to match UFS: when moving (rename(2)) a subdirectorytrasz2008-11-061-0/+38
| | | | | | | from one parent directory to another, in addition to the usual access checks one also needs write access to the subdirectory being moved. Approved by: rwatson (mentor), pjd
* Implement support for RPCSEC_GSS authentication to both the NFS clientdfr2008-11-034-0/+725
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
* #ifdef out the lock-against-self test. I'm not sure it makes sense, anddes2008-10-201-0/+4
| | | | | | it relies on non-portable flock(2) semantics. Not only is flock(2) not portable, but on some OSes that do have it, it is implemented in terms of fcntl(2) locks, which are per-process rather than per-descriptor.
* Update udpzerobyte to understand that passing 0 as a length to recv(2)rwatson2008-10-071-5/+26
| | | | | | | | will cause it to return 0, not EAGAIN. Add UNIX domain socket support to udpzerobyte, which suggests this regression test should be moved to the general sockets test area rather than netinet.
* Add IPv6 support to zero-size UDP transmit/receive test.rwatson2008-10-071-27/+47
|
* Regression test for the loopback handling of zero-length UDP packets, whichrwatson2008-10-072-0/+111
| | | | should be delivered but without payload.
* Add very simple regression test for fstat(2) on sockets: make sure itrwatson2008-10-062-0/+80
| | | | | returns success for various socket types. It's easy to imagine this being enhanced to validate the returned data, but...
* o Correct a comment: a test file size is a four pages not three.maxim2008-09-101-1/+1
|
* Regression tests for bugs in gdtoa.das2008-09-031-11/+17
|
* Update README to reflect removal of netatm/harp test parts some time ago.rwatson2008-08-311-5/+2
| | | | MFC after: 3 days
* Connect a forgotten test case to Makefile.jkim2008-08-291-1/+1
|
* Do not pass validatation level since all issues are fixed now.jkim2008-08-291-1/+1
|
* Merge local copy of bpf_validate() with bpf_filter.c.jkim2008-08-291-11/+14
|
* By default backup geli metadata to a file. It is quite critical 512 bytes,pjd2008-08-2915-17/+123
| | | | | | | | | | | | | | | | | | | | | | | once it is lost, all data is gone. Option '-B none' can by used to prevent backup. Option '-B path' can be used to backup metadata to a different file than the default, which is /var/backups/<prov>.eli. The 'geli init' command also prints backup file location and gives short procedure how to restore metadata. The 'geli setkey' command now warns that even after passphrase change or keys update there could be version of the master key encrypted with old keys/passphrase in the backup file. Add regression tests to verify that new functionality works as expected. Update other regression tests so they don't create backup files. Reviewed by: keramida, rink Dedicated to: a friend who lost 400GB of his live by accidentally overwritting geli metadata MFC after: 2 weeks
* Merge bpf_filter.c r182425 and add test cases for jump range checks.jkim2008-08-296-27/+137
| | | | While I am here, fix stupid typos in test0080.h and make it JIT compiler only.
* Move comments to the right places.jkim2008-08-281-5/+5
|
* Merge bpf_filter.c r182412 and remove additional local checks.jkim2008-08-282-53/+23
| | | | While I am here, use more realistic value for illegal code test case.
* Fix style consistencies and a comment.jkim2008-08-2880-449/+449
|
* Merge bpf_filter.c r182380 and remove additional local checksjkim2008-08-281-12/+4
| | | | for BPF_STX and BPF_LDX|BPF_MEM instructions.
* Add a test case for uninitialized scratch memory (for JIT compiler).jkim2008-08-282-2/+66
|
* Add a test for r182300.stefanf2008-08-272-0/+7
|
* Add a test case for null filter.jkim2008-08-263-11/+35
|
* Add more test cases for invalid instructions and add commentsjkim2008-08-267-9/+232
| | | | about bpf_validate(9) issues.
* Remove some hacks from regression test since bpf_filter.c builds fine now.jkim2008-08-262-9/+8
|
* Add a trivial bpf filter benchmark.jkim2008-08-252-5/+22
|
* Use sys/net/bpf_jitter.c instead of rolling our own versionjkim2008-08-252-10/+7
| | | | since it is compilable on user land now.
OpenPOWER on IntegriCloud