summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Rename use_old_pty variable to use_pts, as this more accurately reflectsrwatson2006-01-281-5/+4
| | | | | | the sense of the variable. Suggested by: dwhite
* Don't try to load KLDs if we're mounting the root. We'd otherwise panic.ssouhlal2006-01-281-4/+12
| | | | | Tested by: kris MFC after: 3 days
* Use $FreeBSD$ for the juggle version, rather than $P4$. This is good forrwatson2006-01-281-1/+1
| | | | | | | | | | | two reasons: (1) juggle is now maintained in CVS, not P4, so the CVS revision number is the authoritative one. (2) Apparently $P4$ requires special handling and juggle was not marked as needing it, resulting in problems for the P4 importer. Requested by: gordon
* Manage the ucred for the NFS server using the crget/crfree API defined incsjp2006-01-284-39/+47
| | | | | | | | | | | | | | | | | | | | kern_prot.c. This API handles reference counting among many other things. Notably, if MAC is compiled into the kernel, it will properly initialize the MAC labels when the ucred is allocated. This work is in preparation for a new MAC entry point which will be responsible for properly initializing policy specific labels for the NFS server credential. Utilization of the crfree/crget APIs reduce the complexity associated with this label's management. Submitted by: green (with changes) [1] Obtained from: TrustedBSD Project Discussed with: rwatson, alfred [1] I moved the ucred allocation outside the scope of the NFS server lock to prevent M_WAIKOK allocations from occurring with non-sleep-able locks held. Additionally, to reduce complexity, the ucred persist as long as the NFS server descriptor.
* s/DT_IA64_PLT_RESERVE/DT_IA_64_PLT_RESERVE/marcel2006-01-283-5/+5
|
* s/R_IA64_/R_IA_64_/marcel2006-01-281-6/+6
|
* Add _rwlock.h, apparently missed from the rwlock.h commit.scottl2006-01-281-0/+39
|
* Squash another invalid use of BUS_DMA_ALLOCNOW.scottl2006-01-281-1/+1
| | | | MFC After: 3 days
* - Add a note that passing NULL to pidfile_write(), pidfile_remove() andpjd2006-01-281-3/+13
| | | | | | | pidfile_close() functions is safe. This possibility is used in example code. - Cast pid_t to int. Requested by: yar
* - Add ports-net-p2p collectionpav2006-01-281-0/+1
|
* Never do programs contain so few bugs as when no debugging toolsdds2006-01-281-0/+4
| | | | | | | are available. -- Niklaus Wirth Pointed by: Panagiotis Louridas
* Back out r1.653; it turns out that the race (or at least the printf) iskris2006-01-281-20/+0
| | | | | | actually not hard to trigger, and it can cause a lot of console spam. Approved by: kan
* - Mention that users need to be in the wheel group to `su - root' by ↵brd2006-01-281-3/+17
| | | | | | | | | | default, and how to change it. PR: docs/70616 Submitted by: Jilles Tjoelker <jilles at stack dot nl> Reviewed by: ru@ Approved by: ceri@ MFC after: 3 days
* lock unused when INVARIANTS not defined, so don't declare it thenimp2006-01-281-0/+2
|
* Add a basic reader/writer lock implementation to the kernel. Thisjhb2006-01-276-0/+783
| | | | | | | | | | | | | | | | | | | | | | | | | | | | implementation is by no means perfect as far as some of the algorithms that it uses and the fact that it is missing some functionality (try locks and upgrades/downgrades are not there yet), however it does seem to work in my local testing. There is more detail in the comments in the code, but the short version follows. A reader/writer lock is very much like a regular mutex: it cannot be held across a voluntary sleep; it can be acquired in an interrupt thread; if the lock is held by a writer then the priority of any threads that block on the lock will be lent to the owner; the simple case lock operations all are done in a single atomic op. It also shares some similiarities with sx locks: it supports reader/writer semantics (multiple readers, but single writers); readers are allowed to recurse, but writers are not. We can extend this implementation further by either improving algorithms or adding new functionality, but this should at least give us a base to work with now. Reviewed by: arch (in theory) Tested on: i386 (4 cpu box with a kernel module that used 4 threads that randomly chose between read locks and write locks that ran w/o panicing for over a day solid. It usually panic'd within a few seconds when there were bugs during testing. :) The kernel module source is available on request.)
* Whitespace.jhb2006-01-271-3/+3
|
* Oops, commit missed file from the previous change to enable multiplejhb2006-01-271-0/+1
| | | | | | queues in turnstiles. Add a new thread member td_tsqueue which contains the sub-queue of a turnstile that a thread is on when it is blocked on a turnstile.
* - Add support for having both a shared and exclusive queue of threads injhb2006-01-273-57/+193
| | | | | | | | | | | | | | | each turnstile. Also, allow for the owner thread pointer of a turnstile to be NULL. This is needed for the upcoming reader/writer lock implementation. - Add a new ddb command 'show turnstile' that will look up the turnstile associated with the given lock argument and display useful information like the list of threads blocked on each queue, etc. If there isn't an active turnstile for a lock at the specified address, then the function will see if there is an active turnstile at the specified address and display info about it if so. - Adjust the mutex code to handle the turnstile API changes. Tested on: i386 (all), alpha, amd64, sparc64 (1 and 3)
* Add a new ddb command 'show sleepq'. It takes a wait channel as anjhb2006-01-271-2/+64
| | | | | | | | | argument and looks for a sleep queue associated with that wait channel. If it finds one it will display information such as the list of threads sleeping on that queue. If it can't find a sleep queue for that wait channel, then it will see if that address matches any of the active sleep queues. If so, it will display information about the sleepq at the specified address.
* Call WITNESS_CHECK() in the page fault handler and immediately assume itjhb2006-01-272-4/+20
| | | | | | | | | | | is a fatal fault if we are holding any non-sleepable locks. This should cut down on the number of bogus LORs we currently get when the kernel panics due to a NULL (or bogus) pointer dereference that goes wandering off into the VM system which tries to acquire locks and then kicks off the spurious LORs. This should probably be ported to all the archs at some point. Tested on: i386
* Add a new macro wrapper WITNESS_CHECK() around the witness_warn() function.jhb2006-01-272-1/+5
| | | | | | | | | | The difference between WITNESS_CHECK() and WITNESS_WARN() is that WITNESS_CHECK() should be used in the places that the return value of witness_warn() is checked, whereas WITNESS_WARN() should be used in places where the return value is ignored. Specifically, in a kernel without WITNESS enabled, WITNESS_WARN() evaluates to an empty string where as WITNESS_CHECK evaluates to 0. I also updated the one place that was checking the return value of WITNESS_WARN() to use WITNESS_CHECK.
* Add a new sysctl, debug.ktr.clear. If you write a non-zero value to thisjhb2006-01-271-0/+20
| | | | | | sysctl then it will clear the KTR buffer. Note that if you have active KTR traces at the same time as a clear operation the behavior is undefined, though it shouldn't panic.
* - Hide 'incorrect geometry warning' in non-interactive mode. A user shouldjkim2006-01-272-22/+36
| | | | | | know what they are doing in non-interactive mode. Less scarier warning goes to debugging info instead. - Print sanitized geometry to debugging info.
* Make sure b_vp and b_bufobj are NULL before calling relpbuf(), as it assertscognet2006-01-271-0/+9
| | | | | | | they are. They should be NULL at this point, except if we're coming from swapdev_strategy(). It should only affect the case where we're swapping directly on a file over NFS.
* Try harder not to recurse.cognet2006-01-271-2/+4
|
* Style: Add blank line after local variable declarations.alc2006-01-271-0/+1
|
* Add some wisdom from Garrett Wollman concerning error codes returned bycperciva2006-01-271-0/+5
| | | | system calls.
* Add `mediaOpen' function. This function mounts selected media device.jkim2006-01-277-0/+36
| | | | | | | | | | | | | | | For example, you can dynamically generate and load configuration file depending on the hardware configuration with the following template: mediaSetCDROM mediaOpen command='/dist/rescue/sh /dist/scripts/install.sh' system mediaClose configFile=/tmp/generated.cfg loadConfig Now we have full access to files on the media before installation begins.
* Have a function pointer to the routine to call for writing an mbufimp2006-01-279-100/+109
| | | | | | | | | | into the card's memory. # this eliminates a more of the ifdef soup in if_ed and if_edvar # I've fixed the cbus drivers, but can't test them all easily. If I've broken anything, please let me know.
* Document the user/group LOR in our sample pf.confmlaier2006-01-271-0/+4
| | | | Submitted by: Devon H. O'Dell
* The .Nm macro prints Open_Disk() instead of libdisk, so use an expliciteharti2006-01-271-2/+2
| | | | argument to get 'libdisk'. Also bump the date of the man page.
* Forced commit because the log message in the previous commit was wrong.harti2006-01-270-0/+0
| | | | Warn people that this library should not be used for anything new.
* Revert 1.45 now that snmp_hostres uses libgeom.harti2006-01-272-0/+8
|
* Merge a bunch of changes that where done in tty_pty.c after tty_pts.c wascognet2006-01-271-104/+7
| | | | forked from it, but missed from some reason.
* Merge from accidental commit to RELENG_5:cperciva2006-01-271-1/+1
| | | | | Correctly identify the host and port values on a failed getaddrinfo lookup.
* Make an example command correct and copyable to terminal.glebius2006-01-271-1/+3
| | | | Submitted by: ru
* Update NGM_PPPOE_GETMODE and NGM_PPPOE_SETMODE descriptions, sinceglebius2006-01-271-12/+30
| | | | new D-Link compat mode is introduced.
* Call NDFREE() only when vn_open() succeeded.pjd2006-01-271-1/+1
| | | | MFC after: 3 days
* Grr. Backout previous change. vn_open_cred() will call NDFREE() on failure.pjd2006-01-271-1/+1
|
* Don't forget to call NDFREE(9) in case of vn_open_cred() failure.pjd2006-01-271-2/+2
| | | | MFC after: 3 days
* o Introduce D-Link compat mode, that is default to off and can be setglebius2006-01-272-64/+87
| | | | | | | | | | by NGM_PPPOE_SETMODE message. When D-Link compat mode is on, we will broadcast PADI with empty Service-Name to all listening hooks. o Rewrite the compatibility options. Before we had two modes - standard and non-standard (aka 3Com). Now we have standard mode and two compat flags, that can be combined. o Be consistent and do s/STUPID/3COM/g. I don't say that 3Com mode isn't stupid, just want to make code easier to read.
* add an option BKTR_USE_FREEBSD_SMBUS that enables compiling the modulejmg2006-01-271-0/+5
| | | | | | with same option... MFC after: 3 days
* Initial import of ce(4) driver for Cronyx Tau-PCI/32 adapters.rik2006-01-276-0/+9271
| | | | Not yet connected to the build.
* make wall(1) work with pts.ume2006-01-271-2/+6
|
* if we are compiling with smbus support, properly depend upon the iic andjmg2006-01-271-0/+7
| | | | | | smbus modules, otherwise as a module you can't kldload bktr... MFC after: 3 days
* Use the new macros abstracting the page coloring/queues implementation.alc2006-01-271-2/+2
| | | | (There are no functional changes.)
* Create mediachg functions for the 3c503 and hpp cards. This is usedimp2006-01-274-33/+28
| | | | | | | | | | | | to properly configure the right interface to use. Also call the mediachg function when we set flags UP and are already running. If this were a pure ifmedia driver, we'd not need to do this since we'd be ignoring the linkX flags. This reduces the number of ifdefs to support sub-devices a little as a nice side effect. It also reduces the number of hpp interfaces exposed by 33%.
* Style(9) issue: return (foo);imp2006-01-271-7/+7
|
* Just like dofilewrite(), call bwillwrite before fo_write.davidxu2006-01-271-0/+2
|
* Transition from ALTPHYS to LINK2. We already document in the ed(4)imp2006-01-272-10/+14
| | | | | | | | | | | | | | | | | man page that the ifconfig option link2 is used to disable the AUI transceiver on the 3com boards (should also say HP PC Lan+). This makes the connection clearer. Add a note about why we set this flag prior to attaching the device. We never set or clear the flag later, only test it. There can be no races here, but this might be asthetically displeasing to some. Also note that we may no longer need to have this knob at all as we may be able to do it with the more sophisticated rc.d scripts we have today I think the only reason it is there is because we didn't used to allow its proper setting when configured to get the IP address via DHCP. I'll note that this would be better handled by using ifmedia for all ed cards, not just those with a miibus...
OpenPOWER on IntegriCloud