summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Clean up PowerPC loader(8) build config.raj2008-02-112-2/+2
| | | | | | | | | | Turn off TFTP support by default: when both TFTP and NFS are enabled in the loader, strange interactions occur in the pure netbooting scenario (i.e. loader is TFTP-ed, kernel+world mounted over NFS), leading to very slow access to the NFS-exported files. Reviewed by: grehan Approved by: cognet (mentor)
* We no longer have both block and character devices, so remove thempp2008-02-111-8/+1
| | | | misleading information stated here.
* Unbreak build, size_t is larger on 64bit platforms.thompsa2008-02-111-1/+1
|
* Explain in more detail how the pass number field works. Bump .Dd.mpp2008-02-111-2/+30
|
* Some small fixes, also introduce an EXAMPLES section.brueffer2008-02-111-3/+3
|
* Typo fix.remko2008-02-111-2/+2
| | | | Spotted by: brueffer
* After issueing a ntpdate [1] I noticed it's already 2008, reflect thatremko2008-02-111-1/+1
| | | | | | in the last modified date. Noticed by: brueffer [1]
* Fix typo (s/existance/existence/)remko2008-02-111-2/+2
| | | | Noticed by: ceri
* Add missing GEOM_LVM option.thompsa2008-02-111-0/+1
|
* Use double precision for z and thus for the entire calculation ofbde2008-02-111-3/+4
| | | | | | | | | | | | | | | | | | | | exp2(i/TBLSIZE) * p(z) instead of only for the final multiplication and addition. This fixes the code to match the comment that the maximum error is 0.5010 ulps (except on machines that evaluate float expressions in extra precision, e.g., i386's, where the evaluation was already in extra precision). Fix and expand the comment about use of double precision. The relative roundoff error from evaluating p(z) in non-extra precision was about 16 times larger than in exp2() because the interval length is 16 times smaller. Its maximum was at least P1 * (1.0 ulps) * max(|z|) ~= log(2) * 1.0 * 1/32 ~= 0.0217 ulps (1.0 ulps from the addition in (1 + P1*z) with a cancelation error when z ~= -1/32). The actual final maximum was 0.5313 ulps, of which 0.0303 ulps must have come from the additional roundoff error in p(z). I can't explain why the additional roundoff error was almost 3/2 times larger than the rough estimate.
* Hook geom_lvm(4) up to the build.thompsa2008-02-115-0/+12
|
* Add a geom class to map Linux LVM logical volumes.thompsa2008-02-113-0/+1378
| | | | | | | | | The logical disks will appear as /dev/lvm/<vol group>-<logical vol>, for instance /dev/lvm/vg0-home. GLVM currently supports linear stripes with segments on multiple physical disks. The metadata is read only, logical volumes can not be allocated or resized. Reviewed by: Ivan Voras
* Clean up coda_pathconf() slightly while debugging a problem there.rwatson2008-02-111-11/+7
| | | | MFC after: 1 month
* Give traceroute6 the ability to traceroute with packets with nodwmalone2008-02-102-48/+111
| | | | | | upper layer header (IP PROTO = 59). Useful for testing firewalls. MFC after: 2 months
* Add support for PC Engines ALIX boards.phk2008-02-101-43/+74
| | | | | | Style cleanup. Hide some messages behind bootverbose.
* - Revert last ehci.c changeattilio2008-02-102-2/+1
| | | | | | | - Include lock.h in lockmgr.h as nested header in order to safely use LOCK_FILE and LOCK_LINE. As long as this code will be replaced soon we can tollerate for a while this namespace pollution even if the real fix would be to let lockmgr() depend by lock.h as a separate header.
* Since we're now actively maintaining the Coda module in the FreeBSD sourcerwatson2008-02-1018-3954/+4002
| | | | | | | | | | | tree, restyle everything but coda.h (which is more explicitly shared across systems) into a closer approximation to style(9). Remove a few more unused function prototypes. Add or clarify some comments. MFC after: 1 month
* After rev. 1.60 of sys/lockmgr.h, the header requires inclusion of thekib2008-02-101-0/+1
| | | | sys/lock.h.
* Add `hw.ciss.nop_message_heartbeat' tunable (default disabled) foriwasaki2008-02-102-1/+10
| | | | | | | | | | | NOP-message polling in ciss_periodic(). Note that setting the tunable to non-zero can be workaround only for `ADAPTER HEARTBEAT FAILED' problem, and may freeze the system w/o the problem. Reviewed by: scottl Reported by: Attila Nagy MFC after: 3 days
* Use LOCK_FILE and LOCK_LINE where necessary instead than __FILE__ andattilio2008-02-091-2/+2
| | | | __LINE__ with lockmgr.
* namei() can call underlying nfs_readlink() passing a struct uio pointerattilio2008-02-093-9/+9
| | | | | | | | | | | | | | owned by a NULL owner. This will lead consequent VOP_ISLOCKED() present into nfs_upgrade_vnlock() to panic as it only acquire curthread now. Fix nfs_upgrade_vnlock() and nfs_downgrade_vnlock() in order to not use more the struct thread pointer passed as argument (as it is really nomore required there as vn_lock() and VOP_UNLOCK doesn't get the lock more). Using curthread, in place, doesn't get ambiguity as LK_EXCLOTHER should be handled as a "not locked" request by both functions. Reported by: kris Tested by: kris Reviewed by: ups
* Fix a few obvious errors in the znew(1) script.yar2008-02-091-4/+3
| | | | | PR: bin/120249 Submitted by: Jaakko Heinonen <see the PR for email>
* As usual, use a minimax polynomial that is specialized for floatbde2008-02-091-7/+8
| | | | | | | | | | | | | | | | | | | | | | | precision. The new polynomial has degree 4 instead of 10, and a maximum error of 2**-30.04 ulps instead of 2**-33.15. This doesn't affect the final error significantly; the maximum error was and is about 0.5015 ulps on i386 -O1, and the number of cases with an error of > 0.5 ulps is increased from 13851 to 14407. Note that the error is only this close to 0.5 ulps due to excessive extra precision caused by compiler bugs on i386. The extra precision could be obtained intentionally, and is useful for keeping the error of the hyperbolic float functions below 1 ulp, since these functions are implemented using expm1f. My recent change for scaling by 2**k had the unintentional side effect of retaining extra precision for longer, so callers of expm1f see errors of more like 0.0015 ulps than 0.5015 ulps, and for the hyperbolic functions this reduces the maximum error from nearly about 2 ulps to about 0.75 ulps. This is about 10% faster on i386 (A64). expm1* is still very slow, but now the float version is actually significantly faster. The algorithm is very sophisticated but not very good except on machines with fast division.
* Various further non-functional cleanups to coda:rwatson2008-02-0910-104/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | - Rename print_vattr to coda_print_vattr and make static, rename print_cred to coda_print_cred. - Remove unused coda_vop_nop. - Add XXX comment because coda_readdir forwards to the cache vnode's readdir rather than venus_readdir, and annotate venus_readdir as unused. - Rename vc_nb_* to vc_*. - Use d_open_t, d_close_t, d_read_t, d_write_t, d_ioctl_t and d_poll_t for prototyping vc_* as that is the intent, don't use our own definitions. - Rename coda_nb_statfs to coda_statfs, rename NB_SFS_SIZ to CODA_SFS_SIZ. - Replace one more OBE reference to NetBSD with a reference to FreeBSD. - Tidy up a little vertical whitespace here and there. - Annotate coda_nc_zapvnode as unused. - Remove unused vcodattach. - Annotate VM_INTR as unused. - Annotate that coda_fhtovp is unused and doesn't match the FreeBSD prototype, so isn't hooked up to vfs_fhtovp. If we want NFS export of Coda to work someday, this needs to be fixed. - Remove unused getNewVnode. - Remove unused coda_vget, coda_init, coda_quotactl prototypes. MFC after: 1 month
* No reason not to maintain stats on statfs in Coda, as it's done forrwatson2008-02-091-3/+3
| | | | | | other VFS operations, so uncomment the existing statistics gathering. MFC after: 1 month
* Remove unused devtomp(), which exploited UFS-specific knowledge to findrwatson2008-02-092-24/+0
| | | | | | | | the mountpoint for a specific device. This was implemented incorrectly, a bad idea in a fundamental sense, and also never used, so presumably a long-idle debugging function. MFC after: 1 month
* Fix a comment about coefficients and expand a related one.bde2008-02-091-2/+2
|
* Since Coda is effectively a stacked file system, use VOP_EOPNOTSUPPrwatson2008-02-092-38/+1
| | | | | | | | for vop_bmap; delete the existing stub that returned either EINVAL or EOPNOTSUPP, and had unreachable calls to VOP_BMAP on the cache vnode. MFC after: 1 month
* WARNS fixes:dwmalone2008-02-094-10/+12
| | | | | | | | | | 1) Add missing parens around assignment that is compared to zero. 2) Make some variables that only take non-negative values unsigned. 3) Some casts/type changes to fix other constness warnings. 4) Make one variable a const char *. 5) Make sure termwidth is positive, it doesn't make sense for it to be negative. Approved by: dds
* Add support for displaying a process' current working directory, rootmarcus2008-02-094-6/+82
| | | | | | | | | | | | | | | | | | | | | | | | directory, and jail directory within procstat. While this functionality is available already in fstat, encapsulating it in the kern.proc.filedesc sysctl makes it accessible without using kvm and thus without needing elevated permissions. The new procstat output looks like: PID COMM FD T V FLAGS REF OFFSET PRO NAME 76792 tcsh cwd v d -------- - - - /usr/src 76792 tcsh root v d -------- - - - / 76792 tcsh 15 v c rw------ 16 9130 - - 76792 tcsh 16 v c rw------ 16 9130 - - 76792 tcsh 17 v c rw------ 16 9130 - - 76792 tcsh 18 v c rw------ 16 9130 - - 76792 tcsh 19 v c rw------ 16 9130 - - I am also bumping __FreeBSD_version for this as this new feature will be used in at least one port. Reviewed by: rwatson Approved by: rwatson
* Lock cache vnode when VOP_FSYNC() is called on a Coda vnode.rwatson2008-02-091-2/+5
| | | | MFC after: 1 month
* Make all calls to vn_lock() in Coda, including recently added ones,rwatson2008-02-092-7/+7
| | | | | | | use LK_RETRY, since failure is undesirable (and not handled). MFC after: 1 month Pointed out by: kib
* The Coda module was originally ported to NetBSD from Mach by rvb, andrwatson2008-02-086-13/+16
| | | | | | | | | | then later to FreeBSD. Update various NetBSD-related comments: in some cases delete them because they don't appply, in others update to say FreeBSD as they still apply but in FreeBSD (and might for that matter no longer apply on NetBSD), and flag one case where I'm not sure whether it applies. MFC after: 1 month
* Fix truncation of lines at LINE_MAX characters by dynamicallyghelmer2008-02-081-15/+61
| | | | | | extending line buffers. PR: bin/76578
* Before invoking vnode operations on cache vnodes, acquire the vnoderwatson2008-02-081-1/+9
| | | | | | | | | | | | | | | | | | locks of those vnodes. Probably, Coda should do the same lock sharing/ pass-through that is done for nullfs, but in the mean time this ensures that locks are adequately held to prevent corruption of data structures in the cache file system. Assuming most operations came from the top layer of Coda and weren't performed directly on the cache vnodes, in practice this corruption was relatively unlikely as the Coda vnode locks were ensuring exclusive access for most consumers. This causes WITNESS to squeal like a pig immediately when Coda is used, rather than waiting until file close; I noticed these problems because of the lack of said squealing. MFC after: 1 month
* Remove undefined coda excluded by #if 1 #else, which previously protectedrwatson2008-02-081-12/+0
| | | | | | | vget() calls using inode numbers to query the root of /coda, which is not needed since we now cache the root vnode with the mountpoint. MFC after: 1 month
* Conver all explicit instances to VOP_ISLOCKED(arg, NULL) intoattilio2008-02-085-12/+13
| | | | | | | | VOP_ISLOCKED(arg, curthread). Now, VOP_ISLOCKED() and lockstatus() should only acquire curthread as argument; this will lead in axing the additional argument from both functions, making the code cleaner. Reviewed by: jeff, kib
* Note m_collapse addition.sam2008-02-081-0/+4
|
* belated bump for the addition of m_collapsesam2008-02-081-1/+1
|
* Introduce -i to SYNOPSIS, forgotten by krion@.ru2008-02-081-1/+1
|
* WARNS fixes: mainly constness and avoid comparing signed withdwmalone2008-02-086-14/+19
| | | | | unsigned by making array indicies unsigned. Also note one or two unused parameters.
* WARNS fixes: remove two unused variables and add some constness.dwmalone2008-02-081-4/+3
|
* Use memcpy(3) instead of the BSD-specific bcopy(3).des2008-02-083-6/+6
| | | | | Submitted by: Joerg Sonnenberger <joerg@britannica.bec.de> MFC after: 2 weeks
* s/MAXPATHLEN/PATH_MAX/ to reflect five-year old change to the code :)des2008-02-081-1/+1
| | | | | Submitted by: Joerg Sonnenberger <joerg@britannica.bec.de> MFC after: 2 weeks
* Fix a bug in lazy deallocation that was introduced whenjasone2008-02-081-7/+10
| | | | | | | | arena_dalloc_lazy_hard() was split out of arena_dalloc_lazy() in revision 1.162. Reduce thundering herd problems in lazy deallocation by randomly varying how many probes a thread does before taking the slow path.
* Fix truncl() when the result should be -0.0L. When the result is +-0.0L,bde2008-02-081-1/+2
| | | | | it must have the same sign as the arg in all rounding modes, but it was always +0.0L.
* Oops, fix the fix in rev.1.10. logb() and logbf() were broken onbde2008-02-081-5/+4
| | | | | | | denormals, and logb() remained broken after 1.10 because the fix for logbf() was incompletely translated. Convert to __FBSDID().
* Clean up manipulation of chunk page map elements to remove some tenuousjasone2008-02-081-362/+357
| | | | | | | | | | | assumptions about whether bits are set at various times. This makes adding other flags safe. Reorganize functions in order to inline i{m,c,p,s,re}alloc(). This allows the entire fast-path call chains for malloc() and free() to be inlined. [1] Suggested by: [1] Stuart Parmenter <stuart@mozilla.com>
* Fix netname() [1] and routename() on big-endian LP64 archs.marius2008-02-072-8/+7
| | | | | Submitted by: Yuri Pankov [1] MFC after: 3 days
* The previous commit message was wrong. It should have read:rink2008-02-070-0/+0
| | | | | | | | | | | | "Fix bootparamd on 64 bit platforms - at least amd64 was broken due to the code believing long == 32 bits and using it to store/compare IPv4 addresses." Note the "== 32 bits" - the previous commit message stated 64 bits, which is plain wrong. PR: bin/112163 Pointed out by: obrien Approved by: imp (mentor, implicit)
OpenPOWER on IntegriCloud