summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* If the quiet flag is specified (-q), don't dump the unread portion ofjhb2008-01-281-1/+4
| | | | the message buffer on startup.
* Add a wrapper function that bound checks writes to the dump device.ru2008-01-2810-46/+61
|
* Correct the kernel config hint in a printf statement.brueffer2008-01-281-1/+1
| | | | | | | Submitted by: R.Mahmatkhanov <cvs-src@yandex.ru> Reviewed by: scottl Approved by: rwatson (mentor) MFC after: 3 days
* Remove references to the obsolete card(4) manpage.brueffer2008-01-284-7/+0
|
* Make sure that the termid type is initialized to AU_IPv4 by default.csjp2008-01-281-0/+2
| | | | | | | | | | | | | | This makes sure that process tokens credentials with un-initialized audit contexts are handled correctly. Currently, when invariants are enabled, this change fixes a panic by ensuring that we have a valid termid family. Also, this fixes token generation for process tokens making sure that userspace is always getting a valid token. This is consistent with what Solaris does when an audit context is un-initialized. Obtained from: TrustedBSD Project MFC after: 1 week
* Don't repeat error logging about NOP message sending ifiwasaki2008-01-281-1/+5
| | | | | | | | ciss_report_request() return an error (which is most likely data underrun). Noticed by: Mark Atkinson MFC after: 1 week
* Only reset driver state when a hardware error is detected.gallatin2008-01-281-5/+6
| | | | | Preserve warning but do not reset if we enter the routine without seeing a hardware error.
* - Fix a comment about prison.rrs2008-01-281-4/+5
| | | | | - Fix it so the VRF is captured while locks are held. MFC after: 1 week
* - Change back to using prioity 0. Which means don't change therrs2008-01-281-1/+1
| | | | | | prioity when running the thread. (this is for the sctp_interator thread). MFC after: 1 week
* - Fix a bug where the socket may have been closed whichrrs2008-01-281-0/+8
| | | | | | could cause a crash in the auth code. Obtained from: Michael Tuexen MFC after: 1 week
* - Fixes a comparison wrap issue with sack gap ack blocks thatrrs2008-01-281-1/+1
| | | | span the 32 bit roll over mark.
* Properly return the error from mls_subject_privileged() in the ifnetrwatson2008-01-281-3/+1
| | | | | | | | | | | | | | | relabel check for MLS rather than returning 0 directly. This problem didn't result in a vulnerability currently as the central implementation of ifnet relabeling also checks for UNIX privilege, and we currently don't guarantee containment for the root user in mac_mls, but we should be using the MLS definition of privilege as well as the UNIX definition in anticipation of supporting root containment at some point. MFC after: 3 days Submitted by: Zhouyi Zhou <zhouzhouyi at gmail dot com> Sponsored by: Google SoC 2007
* Return errno value rather than boolean in this context.iwasaki2008-01-281-2/+6
| | | | MFC after: 1 week
* Adjust the exponent before converting the result from double todas2008-01-281-16/+10
| | | | | float precision. This fixes some double rounding problems for subnormals and simplifies things a bit.
* Revive '-opt' flags which I accidentally removed.keramida2008-01-271-1/+1
| | | | Noticed by: simon
* Enter the sleep state immediately without waiting for timeout ifiwasaki2008-01-271-0/+6
| | | | | | devd(8) is not running such as the system in single user mode. MFC after: 1 week
* Add devctl_process_running() so that power management system driveriwasaki2008-01-272-0/+10
| | | | | | can check whether devd(8) is running. MFC after: 1 week
* Bring the DIAGNOSTICS section in ed.4 closer to reality by removing missingtrhodes2008-01-271-8/+16
| | | | | | diagnostic messages and adding a few found in the code. PR: 51891
* Add a dummynet_enable knob to go with firewall_enable. If this knobmtm2008-01-273-1/+21
| | | | | | | | is enabled dummynet(4) is added to the list of required modules. Discussed on: #freebsd-bugbusters (rwatson, trhodes) PR: conf/79196 MFC after: 1 week
* Run expire even without export hook connected.mav2008-01-271-8/+4
| | | | PR: kern/119839
* Clarify that devfs_system_ruleset should contain a name, not a number.mtm2008-01-271-1/+1
| | | | | | Prompted by PR conf/85363 MFC after: 3 days
* Add the -M command-line option, which will set home directory permissions.mtm2008-01-272-1/+44
| | | | | | | | Works both in interactive or batch mode. This is a heavily modified version of the patch submitted in the PR. PR: bin/105060 MFC after: 1 week
* Fix memory leak when export hook is not connected.mav2008-01-271-0/+2
|
* Remove one very strange unneded if.mav2008-01-271-7/+2
|
* Fix loading for case where we don't overload tcp_usrreqs by calling tcp_drop ↵kmacy2008-01-271-1/+4
| | | | directly
* fix DISABLE_MBUF_IOVEC case by initializing mbuf header completelykmacy2008-01-271-39/+11
|
* Add to the history section.obrien2008-01-271-0/+4
|
* Slightly simplify code.mav2008-01-271-6/+6
|
* - Fix a typo in a comment.marius2008-01-271-8/+10
| | | | | | | | | - Fix whitespace according to style(9). - Sync the comment describing why we have to wait in nsphy_reset() with nsphyter_reset(). It's true that the manual tells to not do a reset within 500us of applying power but that's unlikely the cause of problems seen here. Generally having to wait 500us after a reset however is.
* fts_pathlen is now a size_t rather than an int so a cast is needed.jb2008-01-271-6/+6
| | | | | I'm not sure why warn() and err() string formatted variables need to be right-justified.
* Fix a typo in a comment.marius2008-01-271-1/+1
|
* Add a driver for the National Semiconductor DP83815, DP83843 andmarius2008-01-275-1/+531
| | | | | | | | | | DP83847 PHYs. The main reason for using a specific driver for these PHYs are reset quirks similar to the nsphy(4) driven DP83840A. PR: 112654 Obtained from: NetBSD MFC after: 2 weeks Thanks to: mlaier for testing w/ DP83815
* Sort values according to style.Makefile(5).marius2008-01-271-8/+9
|
* Increase maximum DDB capture buffer size to 5MB.rwatson2008-01-261-1/+1
| | | | | | PR: 119993 MFC after: 2 months Suggested by: Scot Hetzel <swhetzel at gmail dot com>
* Improve multilink receive performance by netgraph item reuse.mav2008-01-261-5/+17
|
* Improve multilink xmit performance by netgraph item reuse.mav2008-01-261-3/+13
|
* Improve multilink receive performance with fragment headers preallocation.mav2008-01-261-22/+23
|
* rx mbufs must have a pkthdr; use m_gethdr to populate the rx ringsam2008-01-261-1/+1
| | | | | | | (and while here correct the mbuf type) Submitted by: Sam Banks <w0lfie@clear.net.nz> MFC after: 1 week
* Allow DDB_CAPTURE_DEFAULTBUFSIZE and DDB_CAPTURE_MAXBUFSIZE to berwatson2008-01-262-13/+20
| | | | | | | | | | | | overridden at compile-time using kernel options of the same names. Rather than doing a compile-time CTASSERT of buffer sizes being even multiples of block sizes, just adjust them at boottime, as the failure mode is more user-friendly. MFC after: 2 months PR: 119993 Suggested by: Scot Hetzel <swhetzel at gmail dot com>
* OLDCARD is gone, release imp's lock.brueffer2008-01-261-1/+0
| | | | Approved by: imp
* OLDCARD is long gone, so finally remove the oldcard.4 manpage.brueffer2008-01-263-246/+3
| | | | Confirmed by: imp
* Our fts(3) API, as inherited from 4.4BSD, suffers from integeryar2008-01-269-112/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fields in FTS and FTSENT structs being too narrow. In addition, the narrow types creep from there into fts.c. As a result, fts(3) consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary user can create, which can have security implications. To fix the historic implementation of fts(3), OpenBSD and NetBSD have already changed <fts.h> in somewhat incompatible ways, so we are free to do so, too. This change is a superset of changes from the other BSDs with a few more improvements. It doesn't touch fts(3) functionality; it just extends integer types used by it to match modern reality and the C standard. Here are its points: o For C object sizes, use size_t unless it's 100% certain that the object will be really small. (Note that fts(3) can construct pathnames _much_ longer than PATH_MAX for its consumers.) o Avoid the short types because on modern platforms using them results in larger and slower code. Change shorts to ints as follows: - For variables than count simple, limited things like states, use plain vanilla `int' as it's the type of choice in C. - For a limited number of bit flags use `unsigned' because signed bit-wise operations are implementation-defined, i.e., unportable, in C. o For things that should be at least 64 bits wide, use long long and not int64_t, as the latter is an optional type. See FTSENT.fts_number aka FTS.fts_bignum. Extending fts_number `to satisfy future needs' is pointless because there is fts_pointer, which can be used to link to arbitrary data from an FTSENT. However, there already are fts(3) consumers that require fts_number, or fts_bignum, have at least 64 bits in it, so we must allow for them. o For the tree depth, use `long'. This is a trade-off between making this field too wide and allowing for 64-bit inode numbers and/or chain-mounted filesystems. On the one hand, `long' is almost enough for 32-bit filesystems on a 32-bit platform (our ino_t is uint32_t now). On the other hand, platforms with a 64-bit (or wider) `long' will be ready for 64-bit inode numbers, as well as for several 32-bit filesystems mounted one under another. Note that fts_level has to be signed because -1 is a magic value for it, FTS_ROOTPARENTLEVEL. o For the `nlinks' local var in fts_build(), use `long'. The logic in fts_build() requires that `nlinks' be signed, but our nlink_t currently is uint16_t. Therefore let's make the signed var wide enough to be able to represent 2^16-1 in pure C99, and even 2^32-1 on a 64-bit platform. Perhaps the logic should be changed just to use nlink_t, but it can be done later w/o breaking fts(3) ABI any more because `nlinks' is just a local var. This commit also inludes supporting stuff for the fts change: o Preserve the old versions of fts(3) functions through libc symbol versioning because the old versions appeared in all our former releases. o Bump __FreeBSD_version just in case. There is a small chance that some ill-written 3-rd party apps may fail to build or work correctly if compiled after this change. o Update the fts(3) manpage accordingly. In particular, remove references to fts_bignum, which was a FreeBSD-specific hack to work around the too narrow types of FTSENT members. Now fts_number is at least 64 bits wide (long long) and fts_bignum is an undocumented alias for fts_number kept around for compatibility reasons. According to Google Code Search, the only big consumers of fts_bignum are in our own source tree, so they can be fixed easily to use fts_number. o Mention the change in src/UPDATING. PR: bin/104458 Approved by: re (quite a while ago) Discussed with: deischen (the symbol versioning part) Reviewed by: -arch (mostly silence); das (generally OK, but we didn't agree on some types used; assuming that no objections on -arch let me to stick to my opinion)
* Generally, anything that runs rc.d scripts internally shouldmtm2008-01-263-5/+5
| | | | start using the quiet prefix (i.e. quietstart, quietstop, etc...).
* Rename DB_ constants in db_capture.c to DDB_ so that when they arerwatson2008-01-261-16/+16
| | | | | | | | exposed as kernel compile options, they have more meaningful names. PR: 119993 MFC after: 2 months Suggested by: Scot Hetzel <swhetzel at gmail dot com>
* Generally, anything that runs rc.d scripts internally shouldmtm2008-01-261-5/+5
| | | | start using the quiet prefix (i.e. quietstart, quietstop, etc...).
* Use 'quietstart' so as not to get spammed with informational diagnostics.mtm2008-01-261-24/+26
|
* Explain how the passno field in /etc/fstab works with fsckmpp2008-01-261-3/+24
| | | | and quotacheck in some more detail.
* Document the no-op -r option of BSD xargs(1).keramida2008-01-261-2/+30
| | | | | | PR: docs/106416 Submitted by: Pete Slagle, freebsd-stable at voidcaptain.com MFC after: 3 days
* Remove Giant acquisition around soreceive() and sosend() in fifofs. Therwatson2008-01-261-10/+4
| | | | | | | | | bug that caused us to reintroduce it is believed to be fixed, and Kris says he no longer sees problems with fifofs in highly parallel builds. If this works out, we'll MFC it for 7.1. MFC after: 3 months Pointed out by: kris
* Sync up quotacheck's preen.c with fsck's. This makes quotacheckmpp2008-01-265-199/+237
| | | | | | | | | process parallel checks in the same way as fsck, since fsck supports pass numbers other than 0, 1 or 2. Without this, quotacheck would ignore file systems with pass numbers > 2. The -l (maxrun) option is now deprecated and can be tuned with pass numbers in /etc/fstab if needed.
OpenPOWER on IntegriCloud