summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix typo in comment.thomas2008-09-021-1/+1
|
* Add simple cd to dvd conversion script.rik2008-08-311-0/+267
|
* 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.
* Reflect sys/net/bpf_jitter.h changes to regression test.jkim2008-08-251-17/+7
|
* Increase cryptotest tool initialization vector (IV) size.raj2008-08-211-1/+1
| | | | | | | | This fixes potential out-of-bound accesses when testing ciphers with block size greater than 8 bytes (e.g. AES). Submitted by: Bartlomiej Sieka tur ! semihalf dot com Discussed with: pjd, sam
* Add test case for 'divide by 0' with BPF_ALU|BPF_DIV|BPF_X instruction.jkim2008-08-182-1/+34
|
* Fix two test cases on 32-bit architectures.jkim2008-08-182-2/+6
|
* Add simple bpf(9) regression tests and test cases.jkim2008-08-1876-0/+2739
|
* Accept tty[ud]0 for console devicephk2008-08-151-1/+1
|
* Use expr -e instead of expr to compute NANO_MEDIASIZE for Flash devicesantoine2008-08-121-5/+5
| | | | | | | | | | larger than 2GB to prevent an overflow [1]. Make case-insensitive comparison work for siliconsystems, soekris and transcend devices. PR: conf/126386 [1] Submitted by: Mark A [1] MFC after: 1 month
* fix syntaxsam2008-08-091-0/+1
|
* Add sbuf_new_auto as a shortcut for the very common case of creating ades2008-08-092-3/+3
| | | | | | | completely dynamic sbuf. Obtained from: Varnish MFC after: 2 weeks
* Add late customize hookphk2008-08-091-0/+25
| | | | | Submitted by: Patrick M. Hausen Sat on for far too long: phk
* Add -i option to supress image building.phk2008-08-091-2/+10
| | | | Submitted by: keramida
* Track /etc/ttys change to uart(4)phk2008-08-091-1/+1
|
* Test that the result is correctly rounded when |y/x| is huge.das2008-08-021-16/+9
|
* use new sysctl to generate a fake radar eventsam2008-08-021-1/+2
|
* Regression tests for fmtcheck(3).das2008-08-022-1/+103
| | | | Obtained from: NetBSD
* Detect if the application has cleared the environ variable by settingscf2008-08-022-25/+70
| | | | | | | | | | | | | | | | | | | | | | | | the first value (environ[0]) to NULL. This is in addition to the current detection of environ being replaced, which includes being set to NULL. Without this fix, the environment is not truly wiped, but appears to be by getenv() until an *env() call is made to alter the enviroment. This change is necessary to support those applications that use this method for clearing environ such as Dovecot and Postfix. Applications such as Sendmail and the base system's env replace environ (already detected). While neither of these methods are defined by SUSv3, it is best to support them due to historic reasons and in lieu of a clean, defined method. Add extra units tests for clearing environ using four different methods: 1. Set environ to NULL pointer. 2. Set environ[0] to NULL pointer. 3. Set environ to calloc()'d NULL-terminated array. 4. Set environ to static NULL-terminated array. Noticed by: Timo Sirainen MFC after: 3 days
* Fix whitespace.scf2008-08-021-52/+52
|
* unset TARGET_CPUTYPE and TARGET_BIG_ENDIAN when building the kernelsam2008-07-311-1/+6
| | | | | | | to silence compiler complaints when cross-building Reviewed by: phk MFC after: 2 weeks
* Add some tests for acos*(), asin*(), atan*(), and atan2*().das2008-07-313-1/+504
|
* Add a regression test for r181017.stefanf2008-07-301-0/+4
| | | | Submitted by: simon
* style(9) specifies that case statements are not indented.scf2008-07-301-1/+1
|
* Remove extra comment that snuck in in last commit.rwatson2008-07-291-3/+0
|
* Add a simple ICMPv6 filter test for IPv6 raw sockets: determine thatrwatson2008-07-292-0/+141
| | | | | | the default ICMPv6 filter is pass all, test that we can set it to block all and restore to pass all. No attempt is made to test that the filtering works, just that we can get and set it.
* Add files to remove when MK_GNU_CPIO = noantoine2008-07-281-0/+6
|
* Add a new program to the multicast test suite. The mcgrab programgnn2008-07-093-1/+270
| | | | | | is used to grab and hold some number of multicast addresses in order to test what happens when an interface goes over the number of multicast addresses it can filter in hardware.
* Add regression tests for fmin{,f,l} and fmax{,f,l}.das2008-07-033-1/+161
| | | | | | | | I wrote these to test amd64 asm functions that used maxss, maxsd, minss, and minsd, but it turns out that those instructions don't handle NaNs and signed zero in the same way as fmin() and fmax() are required to, so we're stuck with the C versions for now.
* Add some regression tests for printf() with positional arguments.das2008-06-292-1/+133
| | | | | | | | | The first test comes from OpenBSD, and the others are additions or adaptations. This is based on OpenBSD's src/regress/lib/libc/sprintf/sprintf_test.c, v1.3. I deliberately did not use v1.4 because it's bogus.
* Rework the lifetime management of the kernel implementation of POSIXjhb2008-06-275-0/+1640
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | semaphores. Specifically, semaphores are now represented as new file descriptor type that is set to close on exec. This removes the need for all of the manual process reference counting (and fork, exec, and exit event handlers) as the normal file descriptor operations handle all of that for us nicely. It is also suggested as one possible implementation in the spec and at least one other OS (OS X) uses this approach. Some bugs that were fixed as a result include: - References to a named semaphore whose name is removed still work after the sem_unlink() operation. Prior to this patch, if a semaphore's name was removed, valid handles from sem_open() would get EINVAL errors from sem_getvalue(), sem_post(), etc. This fixes that. - Unnamed semaphores created with sem_init() were not cleaned up when a process exited or exec'd. They were only cleaned up if the process did an explicit sem_destroy(). This could result in a leak of semaphore objects that could never be cleaned up. - On the other hand, if another process guessed the id (kernel pointer to 'struct ksem' of an unnamed semaphore (created via sem_init)) and had write access to the semaphore based on UID/GID checks, then that other process could manipulate the semaphore via sem_destroy(), sem_post(), sem_wait(), etc. - As part of the permission check (UID/GID), the umask of the proces creating the semaphore was not honored. Thus if your umask denied group read/write access but the explicit mode in the sem_init() call allowed it, the semaphore would be readable/writable by other users in the same group, for example. This includes access via the previous bug. - If the module refused to unload because there were active semaphores, then it might have deregistered one or more of the semaphore system calls before it noticed that there was a problem. I'm not sure if this actually happened as the order that modules are discovered by the kernel linker depends on how the actual .ko file is linked. One can make the order deterministic by using a single module with a mod_event handler that explicitly registers syscalls (and deregisters during unload after any checks). This also fixes a race where even if the sem_module unloaded first it would have destroyed locks that the syscalls might be trying to access if they are still executing when they are unloaded. XXX: By the way, deregistering system calls doesn't do any blocking to drain any threads from the calls. - Some minor fixes to errno values on error. For example, sem_init() isn't documented to return ENFILE or EMFILE if we run out of semaphores the way that sem_open() can. Instead, it should return ENOSPC in that case. Other changes: - Kernel semaphores now use a hash table to manage the namespace of named semaphores nearly in a similar fashion to the POSIX shared memory object file descriptors. Kernel semaphores can now also have names longer than 14 chars (up to MAXPATHLEN) and can include subdirectories in their pathname. - The UID/GID permission checks for access to a named semaphore are now done via vaccess() rather than a home-rolled set of checks. - Now that kernel semaphores have an associated file object, the various MAC checks for POSIX semaphores accept both a file credential and an active credential. There is also a new posixsem_check_stat() since it is possible to fstat() a semaphore file descriptor. - A small set of regression tests (using the ksem API directly) is present in src/tools/regression/posixsem. Reported by: kris (1) Tested by: kris Reviewed by: rwatson (lightly) MFC after: 1 month
* Fix compile on 64-bit platforms.jhb2008-06-261-1/+1
|
* Re-implement the client side of rpc.lockd in the kernel. This implementationdfr2008-06-261-50/+182
| | | | | | | | | | | | provides the correct semantics for flock(2) style locks which are used by the lockf(1) command line tool and the pidfile(3) library. It also implements recovery from server restarts and ensures that dirty cache blocks are written to the server before obtaining locks (allowing multiple clients to use file locking to safely share data). Sponsored by: Isilon Systems PR: 94256 MFC after: 2 weeks
* Enable GCC stack protection (aka Propolice) for userland:ru2008-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64. Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work. Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
OpenPOWER on IntegriCloud