summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Re-implement: do not silently fail when a command is not carriedmtm2008-01-263-3/+18
| | | | | | | | | | | | | | | out because the rc.conf(5) variable was not enabled. Display a message that the command wasn't run and offer suggestions on what the user can do. Implement a quiet prefix, which will disable some diagnostics. The fast prefix also implies quiet. During boot we use either fast or quiet. For shutdown we already use 'faststop'. So, this informational message should only appear during interactive use. An additional benefit of having a quiet prefix is that we can start putting some of our diagnostic messages behind this knob and start "de-cluttering" the console during boot and shutdown.
* Catch up with revision 1.18 of dcons_os.c and add an example of how to usetrhodes2008-01-261-1/+12
| | | | | | | dcons(4) as a valid gdb port. PR: 118490 Submitted by: Alexandre Kovalenko <alex.kovalenko@verizon.net>
* In rev. 1.156, the convertion of the minor number to the unit numberkib2008-01-261-3/+5
| | | | | | | | | | | | resulted in the argument to the make_dev() to be a unit number. Correct this by supplying a minor number to make_dev(), and using the unit number for the calculation of the slave tty name. Reported and tested by: Peter Holm Reviewed by: jhb Yet another pointy hat to: kib MFC after: 1 day
* One of my powerbooks has this chip in it..julian2008-01-261-0/+1
| | | | | | Confirmed by looking at netbsd.. they have also added this. checked by grehen MFC After: 3 days
* Allow arbitrary baud rates, not just the standard ones.emaste2008-01-261-22/+14
|
* add opt_global.h dependencykmacy2008-01-261-1/+1
|
* Fix a harmless type error in 1.9.bde2008-01-251-1/+1
|
* Fix a bug where a thread that hit the race where the sleep timeout firesjhb2008-01-251-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | while the thread does not hold the thread lock would stop blocking for subsequent interruptible sleeps and would always immediately fail the sleep with EWOULDBLOCK instead (even sleeps that didn't have a timeout). Some background: - KSE has a facility for allowing one thread to interrupt another thread. During this process, the target thread aborts any interruptible sleeps much as if the target thread had a pending signal. Once the target thread acknowledges the interrupt, normal sleep handling resumes. KSE manages this via the TDF_INTERRUPTED flag. Specifically, it sets the flag when it sends an interrupt to another thread and clears it when the interrupt is acknowledged. (Note that this is purely a software interrupt sort of thing and has no relation to hardware interrupts or kernel interrupt threads.) - The old code for handling the sleep timeout race handled the race by setting the TDF_INTERRUPT flag and faking a KSE-style thread interrupt to the thread in the process of going to sleep. It probably should have just checked the TDF_TIMEOUT flag in sleepq_catch_signals() instead. - The bug was that the sleepq code would set TDF_INTERRUPT but it was never cleared. The sleepq code couldn't safely clear it in case there actually was a real KSE thread interrupt pending for the target thread (in fact, the sleepq timeout actually stomped on said pending interrupt). Thus, any future interruptible sleeps (*sleep(.. PCATCH ..) or cv_*wait_sig()) would see the TDF_INTERRUPT flag set and immediately fail with EWOULDBLOCK. The flag could be cleared if the thread belonged to a KSE process and another thread posted an interrupt to the original thread. However, in the more common case of a non-KSE process, the thread would pretty much stop sleeping. - Fix the bug by just setting TDF_TIMEOUT in the sleepq timeout code and not messing with TDF_INTERRUPT and td_intrval. With yesterday's fix to fix sleepq_switch() to check TDF_TIMEOUT, this is now sufficient. MFC after: 3 days
* Update the timestamp regexps in syncstamp() and monostamp() for > 99999jhb2008-01-251-2/+2
| | | | | traces where there isn't any leading whitespace before the record number in the ktrdump output.
* Backout previous commit. It's going to clutter the consolemtm2008-01-251-3/+0
| | | | | | | | | | during boot and shutdown. I think I'll hide it behind autoboot or maybe take brooks@ suggestion and implement a different command prefix for booting/shutdown purposes, but in any case it needs more thought and attention. Noticed by: ceri Pointyhat to: mtm
* Clarify in what formats the grouplist for the '-G' switch may be accepted.mtm2008-01-251-1/+1
| | | | Submitted by: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
* If the rc.conf(5) variable for a script is not enabled do not failmtm2008-01-251-0/+3
| | | | | | | | silently. Display a message that the command wasn't run and make possible suggestions for what to do. PR: conf/118770 MFC after: 1 week
* Hide ipfw internal data structures behind IPFW_INTERNAL rather thanrwatson2008-01-253-0/+16
| | | | | | | | | | exposing them to all consumers of ip_fw.h. These structures are used in both ipfw(8) and ipfw(4), but not part of the user<->kernel interface for other applications to use, rather, shared implementation. MFC after: 3 days Reported by: Paul Vixie <paul at vix dot com>
* Rev. 1.6 made it impossible to use rc.d/kerberos with the krb5 port.mtm2008-01-252-2/+1
| | | | | | | | Re-implement the change so that the script once again works with the krb5 port. Submitted by: kensmith (slightly modified) MFC after: 3 days
* Calculate baud rate divisor instead of allowing only a fixed set ofemaste2008-01-252-35/+71
| | | | | | | | | | standard rates. Obtained from OpenBSD src/sys/dev/usb/uftdi.c 1.29 src/sys/dev/usb/uftdireg.h 1.11 OpenBSD revisions noted by: ticso, on hackers
* Fix a race in the sleepqueue timeout code that resulted in sleeps notjhb2008-01-251-4/+25
| | | | | | | | | | | | | | | | | | | | | | | | | being properly cancelled by a timeout. In general there is a race between a the sleepq timeout handler firing while the thread is still in the process of going to sleep. In 6.x with sched_lock, the race was largely protected by sched_lock. The only place it was "exposed" and had to be handled was while checking for any pending signals in sleepq_catch_signals(). With the thread lock changes, the thread lock is dropped in between sleepq_add() and sleepq_*wait*() opening up a new window for this race. Thus, if the timeout fired while the sleeping thread was in between sleepq_add() and sleepq_*wait*(), the thread would be marked as timed out, but the thread would not be dequeued and sleepq_switch() would still block the thread until it was awakened via some other means. In the case of pause(9) where there is no other wakeup, the thread would never be awakened. Fix this by teaching sleepq_switch() to check if the thread has had its sleep canceled before blocking by checking the TDF_TIMEOUT flag and aborting the sleep and dequeueing the thread if it is set. MFC after: 3 days Reported by: dwhite, peter
* Once the release goes out, RELENG_7_* will need approval from so@.cperciva2008-01-241-0/+1
| | | | Approved by: core (two months ago)
* Move the code for working with kld's out into its own file.jhb2008-01-244-269/+306
|
* When asked to use kqueue, AIO stores its internal state in thedumbbell2008-01-242-4/+8
| | | | | | | | | | | | | `kn_sdata' member of the newly registered knote. The problem is that this member is overwritten by a call to kevent(2) with the EV_ADD flag, targetted at the same kevent/knote. For instance, a userland application may set the pointer to NULL, leading to a panic. A testcase was provided by the submitter. PR: kern/118911 Submitted by: MOROHOSHI Akihiko <moro@remus.dti.ne.jp> MFC after: 1 day
* Do not dereference NULL scp in the case the screen is not opened.kib2008-01-241-0/+2
| | | | | | | | Instead, return ENXIO to the ioctl caller. Reported and tested by: Pawel Worach <pawel.worach gmail com> Discussed with: markus MFC after: 3 days
* Reflect lockcount() axing and lockmgr() prototype changing.attilio2008-01-241-20/+2
|
* - sched_4bsd is no longer a default system scheduler on someru2008-01-242-13/+5
| | | | | | | | | | architectures, so call it "traditional" instead. - sched_ule is no longer buggy or experimental (according to rev. 1.7 of sched_ule(4)), so don't call it experimental (reported by a user on stable@). Reviewed by: rwatson
OpenPOWER on IntegriCloud