summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Restore standard behavior: log to console only when normal loggingglebius2004-12-241-2/+3
| | | | | | | | | failed, not always. PR: bin/75356 Submitted by: Mark Knight <markk knigma org> Pointy hat to: glebius MFC after: 3 days
* Enable fine grained locking within IPFilter, using mtx(9) and sx(9) allowingdarrenr2004-12-249-27/+81
| | | | the the "needs giant" flag to be removed from the driver.
* ``NULL is a specific instance of a null pointer constant; the generic iskeramida2004-12-236-30/+12
| | | | | | | | | | | | | a "null pointer".'' Making good use of the excellent explanations sent to me by Ruslan Ermilov, Garrett Wollman and Bruce Evans, correct the descriptions of null pointers. They are just "null pointers", not nil, not NULL or ".Dv NULL". Suggested by: ru, wollman, bde Reviewed by: ru, wollman Pointy hat: keramida
* Fix creation on "dlciX" hook in ng_sample.rik2004-12-231-2/+3
| | | | | Approved by: julian MFC after: 3 days
* Turn NFS directio off until the stability issues are resolved.ps2004-12-231-1/+1
|
* Update disk->d_genid field when increasing sc->sc_genid.pjd2004-12-231-0/+1
|
* - Give the timer, thermal, and error LVT entries an interrupt vector evenjhb2004-12-231-22/+30
| | | | | | | | | | | | | | though these aren't used yet. - Add missing function prototypes for some static functions. - Allow lvt_mode() to handle an LVT entry with a delivery mode of fixed. - Consolidate code duplicated in lapic_init() and lapic_setup() to program the spurious vector register of a local APIC in a static lapic_enable() function. - Dump the timer, thermal, error, and performance counter LVT entries during lapic_dump(). - Program LVT pins (currently only LINT0 and LINT1) after the local APIC has been software enabled via lapic_enable() since otherwise the LVT programming will not be able to unmask LVT sources.
* Some small style fixes.jhb2004-12-231-3/+2
|
* Add some constants for the local APIC timer.jhb2004-12-231-0/+5
|
* Add a simple 'intrcnt_add' function that other MD code can use to add ajhb2004-12-232-0/+12
| | | | | single named counter to the interrupt counts without having to fake up an entire interrupt source.
* Modify pmap_enter_quick() so that it expects the page queues to be lockedalc2004-12-2311-30/+19
| | | | | | | | | | | on entry and it assumes the responsibility for releasing the page queues lock if it must sleep. Remove a bogus comment from pmap_enter_quick(). Using the first change, modify vm_map_pmap_enter() so that the page queues lock is acquired and released once, rather than each time that a page is mapped.
* - Add a function to set the Task Priority Register (TPR) of the local APIC.jhb2004-12-232-18/+39
| | | | | | | | | | | | | | | Currently this is only used to initiailize the TPR to 0 during initial setup. - Reallocate vectors for the local APIC timer, error, and thermal LVT entries. The timer entry is allocated from the top of the I/O interrupt range reducing the number of vectors available for hardware interrupts to 191. Linux happens to use the same exact vector for its timer interrupt as well. If the timer vector shared the same priority queue as the IPI handlers, then the frequency that the timer vector will eventually be firing at can interact badly with the IPIs resulting in the queue filling and the dreaded IPI stuck panics, hence it being located at the top of the previous priority queue instead. - Fixup various minor nits in comments.
* Fix counting length of leadin for hook name (sizeof () => strlen ()).rik2004-12-231-1/+1
| | | | | Approved by: julian MFC after: 3 days
* Warn about the NOFOO -> NO_FOO conversion, and remind users toru2004-12-231-0/+7
| | | | | read the COMMON ITEMS section of this file for proper upgrade instructions.
* Move systm.h up, since it is required by mbuf.h.glebius2004-12-231-1/+1
| | | | Requested by: ru
* - sort includesglebius2004-12-231-5/+4
| | | | - remove duplicate include sys/sysctl.h
* Don't call "objs" target in rescue.mk twice.ru2004-12-231-1/+1
|
* Make "===> " prefixes look sane.ru2004-12-231-6/+13
|
* Include bsd.compat.mk early from sys.mk, enough for makefilesru2004-12-232-1/+1
| | | | | | | using conditional statements to see the new spellings of NO_* knobs (in case user still uses old spellings). Reported by: kris
* Document the 2130SLPscottl2004-12-231-1/+3
|
* Add OZ711M1imp2004-12-231-0/+2
| | | | Submitted by: Gordon Bergling
* Add recognition of O2Micro 711M1.imp2004-12-232-0/+2
| | | | Submitted by: Gordon Bergling
* Better rendering of the prototype for signal(3).jkoshy2004-12-231-6/+14
| | | | Suggested by: ru
* Assert the sem lock in sem_ref() and sem_rel(), as it is required torwatson2004-12-231-0/+2
| | | | safely manipulate the reference count.
* Attempt to consistently use () around return values in calls torwatson2004-12-232-36/+36
| | | | return() in newer code (sysctl, ISN, timewait).
* Remove an XXXRW comment relating to whether or not the TCP timers arerwatson2004-12-232-12/+2
| | | | | | | | MPSAFE: they are now believed to be. Correct a typo in a second comment. MFC after: 2 weeks
* Remove the now unused tcp_canceltimers() function. tcpcb timers arerwatson2004-12-232-16/+0
| | | | | | now stopped as part of tcp_discardcb(). MFC after: 2 weeks
* Remove an annotation of a minor race relating to the update ofrwatson2004-12-231-7/+0
| | | | | | | | | multiple MIB entries using sysctl in short order, which might result in unexpected values for tcp_maxidle being generated by tcp_slowtimo. In practice, this will not happen, or at least, doesn't require an explicit comment. MFC after: 2 weeks
* Remove temporary debugging printf that was used to detect the presencerwatson2004-12-231-4/+0
| | | | | | | of a race that had previously caused a panic in order to determine if the fix was for the right problem. It was. MFC after: 2 weeks
* In sonewconn(), the s/if/while/ change to wait for room at the tail ofrwatson2004-12-232-10/+10
| | | | | the accept queue is a feature, not a bug/issue, so remove the XXXRW from the comment.
* Remove an XXXRW indicating atomic operations might be used as arwatson2004-12-231-12/+4
| | | | | | | | | | | | | | | | substitute for a global mutex protecting the socket count and generation number. The observation that soreceive_rcvoob() can't return an mbuf chain is a property, not a bug, so remove the XXXRW. In sorflush, s/existing/previous/ for code when describing prior behavior. For SO_LINGER socket option retrieval, remove an XXXRW about why we hold the mutex: this is correct and not dubious. MFC after: 2 weeks
* In soalloc(), simplify the mac_init_socket() handling to removerwatson2004-12-231-14/+3
| | | | | | | | | | | unnecessary use of a global variable and simplify the return case. While here, use ()'s around return values. In sodealloc(), remove a comment about why we bump the gencnt and decrement the socket count separately. It doesn't add substantially to the reading, and clutters the function. MFC after: 2 weeks
* Fix a couple of typos.keramida2004-12-231-2/+4
| | | | | | PR: docs/75410 Submitted by: "Paul A.Hoadley" <paulh@logicsquad.net> MFC after: 3 days
* - Add genid field to the metadata which will allow to improve reliability a bit.pjd2004-12-224-57/+186
| | | | | | | | | | | | | | | | After this change, when component is disconnected because of an I/O error, it will not be connected and synchronized automatically, it will be logged as broken and skipped. Autosynchronization can occur, when component is disconnected (on orphan event) and connected again - there were no I/O error, so there is no need to not connected the component, but when there were writes while it wasn't connected, it will be synchronized. This fix cases, when component is disconnected because of I/O error and can be connected again and again. - Bump version number. - Add version change history. - Implement backward compatibility mechanism. After this change when metadata in old version is detected, it is automatically upgraded to the new (current) version.
* Further fix the case mentioned in rev. 1.302. Theru2004-12-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | intent was (and still is) that if a user has say CPUTYPE=i686 set in /etc/make.conf, we don't print the assignment type warning unless TARGET_CPUTYPE is overridden. Unfortunately, the implementation was buggy, and only recent changes to bsd.cpu.mk that swapped canonical and alias values of some CPU types made the bug apparent. Here's what happens here. - CPUTYPE=i686 is set in /etc/make.conf, - bsd.cpu.mk reset it to "pentiumpro", - Makefile.inc1 compares this canonical value with the result of the following test, make -f /dev/null CPUTYPE=pentiumpro -V CPUTYPE and expects the result to be "pentiumpro" too, but "i686" is returned, here's why. We have two CPUTYPE variables, global, set to "i686" in /etc/make.conf, and command-line (of a higher precedence), set to "pentiumpro". The following part of bsd.cpu.mk, . elif ${CPUTYPE} == "i686" CPUTYPE = pentiumpro which is responsible for converting aliases to canonical values, sees the value of the CPUTYPE command-line variable first, "pentiumpro", and no conversion is done -- the net effect is that CPUTYPE global stays with its old value "i686", and "make -V CPUTYPE" (which prints variables in the global context) returns "i686". The fix was to pass the CPUTYPE in the test above as an environment variable instead of as a command line variable, i.e., CPUTYPE=pentiumpro make -f /dev/null -V CPUTYPE This time, CPUTYPE global is still set to "i686" initially (by /etc/make.conf), and an envieronment variable CPUTYPE (of a lower precedence) is set to "pentiumpro". The .elif sees it's set to "i686" and resets it to "pentiumpro", and so "make -V" returns "pentiumpro". NB: these various types of make(1) variables can be very painful, especially when combined with "make -V".
* Add send buffer locking to uipc_send(). Without this locking a race canalc2004-12-221-0/+3
| | | | | | | | | occur between a reader and a writer that results in a panic upon close, e.g., "panic: sbflush_locked: cc 4 || mb 0xffffff0052afa400 || mbcnt 0" Reviewed by: rwatson@ MFC after: 2 weeks
* 'forget' command takes device names, not provider names.pjd2004-12-221-1/+1
|
* Include fcntl.hphk2004-12-221-2/+3
| | | | | | Include selinfo.h (don't rely on vnode.h to do so) Check O_NONBLOCK instead of IO_NELAY Don't include vnode.h
* Don't include filedesc.hphk2004-12-221-3/+3
| | | | | | | Include fcntl.h Include selinfo.h (don't rely on vnode.h to do so) Check O_NONBLOCK instead of IO_NDELAY Don't include vnode.h
* Include fcntl.hphk2004-12-221-3/+3
| | | | | | | Check O_NONBLOCK instead of IO_NDELAY Include uio.h Don't include vnode.h Don't include filedesc.h
* Include uio.hphk2004-12-221-3/+3
| | | | | Check O_NONBLOCK instead if IO_NDELAY Don't include vnode.h
* Include fcntl.hphk2004-12-221-3/+4
| | | | | | Check O_NONBLOCK instead of IO_NDELAY. Include selinfo.h instead of relying on vnode.h to do so. Don't include vnode.h
* Include fcntl.hphk2004-12-221-2/+2
| | | | | check O_NONBLOCK instead of IO_NDELAY Don't include vnode.h.
* Include fcntl.hphk2004-12-221-2/+2
| | | | | check O_NONBLOCK instead of IO_NDELAY don't include vnode.h
* Include fcntl.hphk2004-12-221-2/+2
| | | | | Check O_NONBLOCK instead of IO_NDELAY Don't include vnode.h
* Check O_NONBLOCK instead of IO_NDELAY.phk2004-12-221-2/+1
| | | | Don't include <sys/vnode.h>
* Fix comment.phk2004-12-222-2/+2
|
* Don't include vnode.h.phk2004-12-221-3/+2
| | | | Check O_NONBLOCK instead of IO_NDELAY
* Correct speling erors.wollman2004-12-221-2/+2
|
* Don't include vnode.hphk2004-12-221-1/+0
|
OpenPOWER on IntegriCloud