summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Revert the previous commit and add a comment explaining why it was wrong.des2011-10-221-2/+14
|
* openpam_static.c isn't auto-generated.des2011-10-221-5/+2
|
* Fix a race: we should update sc_len before dropping the pf lock, otherwise aglebius2011-10-211-3/+1
| | | | | | number of packets can be queued on sc, while we are in ip_output(), and then we wipe the accumulated sc_len. On next pfsync_sendout() that would lead to writing beyond our mbuf cluster.
* Update per-thread I/O statistics collection in ZFS.pjd2011-10-212-2/+9
| | | | | | | | | This allows to see processes I/O activity in 'top -m io' output. PR kern/156218 Reported by: Marcus Reid <marcus@blazingdot.com> Patch by: avg MFC after: 3 days
* Spelling.glebius2011-10-211-1/+1
| | | | Submitted by: dougb
* Minor corrections and clarifications regarding exceptions.das2011-10-211-12/+23
|
* zfs vdev_file_io_start: validate vdev before using vdev_tsdpjd2011-10-211-8/+10
| | | | | | | | vdev_tsd can be NULL for certain vdev states. At least in userland testing with ztest. Submitted by: avg MFC after: 3 days
* zdb: access dp_free_bpobj only if pool version is >= SPA_VERSION_DEADLISTSpjd2011-10-211-2/+4
| | | | | Submitted by: avg MFC after: 3 days
* thr_create: new_thread_ID may be NULLpjd2011-10-211-1/+5
| | | | | Submitted by: avg MFC after: 3 days
* Note that it is still not possible to guard special kind of allocations, thoseglebius2011-10-211-1/+15
| | | | that have special relationships with uma(9). Currently only mbuf clusters.
* libzpool task_alloc: pass only valid flags to kmem_allocpjd2011-10-211-1/+1
| | | | | | | | tqflags may contain other flags besided those that are suitable for kmem_alloc == umem_alloc Submitted by: avg MFC after: 3 days
* Because ZFS boot code was very fragile in the past and real PITA to debug,pjd2011-10-212-0/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | introduce zfsboottest.sh script that will verify if it will be possible to boot from the given pool. # zfsboottest.sh system Where "system" is pool name of the pool we want to boot from. What is being verified by the script: - Does the pool exist? - Does it have bootfs property configured? - Is mountpoint property of the boot dataset set to 'legacy'? Dataset configured in bootfs property has to be mounted to perform more checks: - Does the /boot directory in boot dataset exist? - Is this dataset configured as root file system in /etc/fstab or set in vfs.root.mountfrom variable in /boot/loader.conf? By using zfsboottest tool the script will read all the files in /boot directory using ZFS boot code and calculate their checksums. Then, it will walk /boot directory using find(1) though regular file sytem and also read all the files in /boot directory and calculate their checksums. If any of the files cannot be looked up, read or checksum is invalid it will be reported and booting off of this pool is probably not possible. Some additional checks may be interesting as well. For example if the disks contain proper pmbr and gptzfsboot code or if all expected files in /boot/ are present. When upgrading FreeBSD, one should snapshot datasets that contain operating system, upgrade (install new world and kernel) and use zfsboottest.sh to verify if it will be possible to boot from new configuration. If all is good one should upgrade boot blocks, by eg.: # gpart -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 If something is wrong, one should rollback datasets and report the problems. MFC after: 3 days
* - Allow to specify multiple files to check, eg.pjd2011-10-212-35/+69
| | | | | | | | | | zfsboottest gpt/system0 gpt/system1 - /boot/kernel/kernel /boot/zfsloader - Instead of printing file's content calculate MD5 hash of the file, so it can be easly compared to the hash calculated via file system. - Some other minor improvements. MFC after: 3 days
* Add missing #includes.ed2011-10-212-0/+3
| | | | | | | | | According to POSIX, these two header files should be able to be included by themselves, not depending on other headers. The <net/if.h> header uses struct sockaddr when __BSD_VISIBLE=1, while <netinet/tcp.h> uses integer datatypes (u_int32_t, u_short, etc). MFC after: 2 months
* In FreeBSD ip_output() expects ip_len and ip_off in host byte orderglebius2011-10-211-0/+8
| | | | PR: kern/159029
* It turns out that truss also used kdump's mkioctls script, and expecteddes2011-10-214-20/+38
| | | | | | | | | | | | ioctlname() to return a pointer to the name rather than print it. This did not show up in testing because truss had its own prototype for ioctlname(), so it would build fine and run fine as long as the program being traced did not issue an ioctl. Teach mkioctls to generate different versions of ioctlname() based on its first command-line argument. Pointed out by: Garrett Cooper <yanegomi@gmail.com>
* People porting FreeBSD to new architectures ought not have todas2011-10-218-17/+44
| | | | | | | | | | | | | implement a deprecated FPU control interface in addition to the standard one. To make this clearer, further deprecate ieeefp.h by not declaring the function prototypes except on architectures that implement them already. Currently i386 and amd64 implement the ieeefp.h interface for compatibility, and for fp[gs]etprec(), which doesn't exist on most other hardware. Powerpc, sparc64, and ia64 partially implement it and probably shouldn't, and other architectures don't implement it at all.
* Replace a proliferation of buggy MD implementations of modf() with adas2011-10-2128-987/+149
| | | | | | | working MI one. The MI one only needs to be overridden on machines with non-IEEE754 arithmetic. (The last supported one was the VAX.) It can also be overridden if someone comes up with a faster one that actually passes the regression tests -- but this is harder than it sounds.
* Add regression tests for modf{,f,l}().das2011-10-211-26/+108
|
* Add support for the 'x' mode option in fopen() as specified in the C1Xdas2011-10-212-49/+60
| | | | | | draft standard. The option is equivalent to O_EXCL. MFC after: 1 month
* Tests for complex trig and hyperbolic functions.das2011-10-213-1/+552
|
* Tests for cancellation in fma(). Also include more tests for 128-bitdas2011-10-211-3/+63
| | | | | long doubles. Thanks for clusteradm (simon) for making the needed hardware available.
* Fix a regression introduced in r226371: When the high part of x*ydas2011-10-212-6/+6
| | | | | exactly cancels with z, return the low part of x*y instead of discarding it.
* Fix a corner case: tan(large + Inf i) == NaN + NaN i.das2011-10-212-0/+10
|
* Improved handling of large x in ccosh{,f}():das2011-10-214-15/+83
| | | | | | | | | - Handle cases where exp(x) would overflow, but ccosh(x) ~= exp(x) / 2 shouldn't. - Use the ccosh(x) ~= exp(x) / 2 approximation to simplify the calculation when x is large. Similarly for csinh(). Also fixed the return value of csinh(-Inf +- 0i).
* Use __ldexp_exp() to simplify things and improve accuracy for x neardas2011-10-214-27/+10
| | | | the overflow threshold.
* The cexp() and {,c}{cos,sin}h functions all need to be able to computedas2011-10-216-33/+210
| | | | | | | | | | | exp(x) scaled down by some factor, and the challenge is doing this accurately when exp(x) would overflow. This change replaces all of the tricks we've been using with common __ldexp_exp() and __ldexp_cexp() routines that handle all the scaling. bde plans to improve on this further by moving the guts of exp() into k_exp.c and handling the scaling in a more direct manner. But the current approach is simple and adequate for now.
* Use STRICT_ASSIGN() to ensure that the compiler doesn't screw thingsdas2011-10-214-5/+13
| | | | | | up by storing x in a wider type than it's supposed to. Submitted by: bde
* Per IEEE754r, pow(1, y) is 1 even if y is NaN, and pow(-1, +-Inf) is 1.das2011-10-212-2/+8
| | | | MFC after: 2 weeks
* Bugfix: feenableexcept() and fedisableexcept() should just return thedas2011-10-212-8/+8
| | | | | | old exception mask, not mask | ~FE_ALL_EXCEPT. MFC after: 2 weeks
* Make all the lines align properly.pjd2011-10-201-4/+4
| | | | MFC after: 3 days
* With LOADER_MBR_SUPPORT defined and LOADER_GPT_SUPPORT undefined we wouldpjd2011-10-201-2/+3
| | | | | | | never call disk_openmbr(). Submitted by: avg MFC after: 3 days
* - Correctly read gang header from raidz.pjd2011-10-202-57/+60
| | | | | | | | | | - Decompress assembled gang block data if compressed. - Verify checksum of a gang header. - Verify checksum of assembled gang block data. - Verify checksum of uber block. Submitted by: avg MFC after: 3 days
* Build 'dtc' by default for MIPS.jchandra2011-10-201-2/+3
| | | | | | | The device tree compiler is needed during the kernel build to compile DTS files to DTB. Reviewed by: stas
* Fix missing return when LOADER_GPT_SUPPORT is defined, but LOADER_MBR_SUPPORTpjd2011-10-191-1/+1
| | | | | | is not. MFC after: 3 days
* Always pass data size for checksum verification function, as usingpjd2011-10-192-11/+11
| | | | | | | | | | physical block size declared in bp may not always be what we want. For example in case of gang block header physical block size declared in bp is much larger than SPA_GANGBLOCKSIZE (512 bytes) and checksum calculation failed. This bug could lead to accessing unallocated memory and resets/failures during boot. MFC after: 3 days
* Never pass NULL block pointer when reading. This is neither expected norpjd2011-10-191-1/+2
| | | | | | | | handled by lower layers like vdev_raidz, which uses bp for checksum verification. This bug could lead to NULL pointer reference and resets during boot. MFC after: 3 days
* Don't mark vdev as healthy too soon, so we won't try to use invalid vdevs.pjd2011-10-191-2/+1
| | | | MFC after: 3 days
* Initialize 'rc' properly before using it. This error could lead to infinitepjd2011-10-191-1/+3
| | | | | | loop when data reconstruction was needed. MFC after: 3 days
* Remove redundant size calculation.pjd2011-10-191-5/+0
| | | | MFC after: 3 days
* Add a warning about why sbp(4) is commented out so that curious folkskensmith2011-10-195-0/+5
| | | | | | | are forewarned they might wind up with a hole in their foot if they decide to give it a try. Suggested by: dougb
* If ls was invoked with -i but neither -l nor -s, blocksize was used indes2011-10-191-2/+2
| | | | | | | display() to calculate column widths, but was not initialized in main(). This resulted in a division by zero. Noticed by: Michael Butler <imb@protected-networks.net>
* Keep FDT options commented until dtc is build by default for mipsjchandra2011-10-192-6/+6
| | | | Otherwise automated builds will fail for XLP and XLP64
* Fix recursive pf locking leading to panics. Splatter PF_LOCK_ASSERT()sbz2011-10-191-20/+22
| | | | | | | | | | | | | to document where we are expecting to be called with a lock held to more easily catch unnoticed code paths. This does not neccessarily improve locking in pfsync, it just tries to avoid the panics reported. PR: kern/159390, kern/158873 Submitted by: pluknet (at least something that partly resembles my patch ignoring other cleanup, which I only saw too late on the 2nd PR) MFC After: 3 days
* latin1 -> utf8des2011-10-198-9/+9
|
* De-virtualize the pf_task_mtx lock. At the current state of pf lockingbz2011-10-192-20/+14
| | | | | | | | | and virtualization it is not helpful but complicates things. Current state of art is to not virtualize these kinds of locks - inp_group/hash/info/.. are all not virtualized either. MFC after: 3 days
* Adjust the PF_ASSERT() macro to what we usually use in the network stack:bz2011-10-194-16/+18
| | | | | | PF_LOCK_ASSERT() and PF_UNLOCK_ASSERT(). MFC after: 3 days
* Add new USB IDs to RUN driver. Update usb.conf.hselasky2011-10-193-9/+79
| | | | | PR: usb/161798 MFC after: 3 days
* In the non-FreeBSD case we do not expect PF_LOCK and friends to do anything.bz2011-10-191-13/+4
| | | | MFC after: 3 days
* Pseudo interfaces should go at SI_SUB_PSEUDO. However at leastbz2011-10-193-4/+4
| | | | | | | | | | | | | pfsync also depends on pf to be initialized already so pf goes at FIRST and the interfaces go at ANY. Then the (VNET_)SYSINIT startups for pf stays at SI_SUB_PROTO_BEGIN and for pfsync we move to the later SI_SUB_PROTO_IF. This is not ideal either but at least an order that should work for the moment and can be re-fined with the VIMAGE merge, once this will actually work with more than one network stack. MFC after: 3 days
OpenPOWER on IntegriCloud