summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Do not depend on namespace pollution, explicitly include sys/sx.hkan2003-03-121-0/+1
|
* fix module building; drivers now require opt_{ubsec,hifn}.hsam2003-03-112-2/+8
|
* FIPS 140-2 rng data tester for h/w crypto devices. This driver periodicallysam2003-03-112-0/+455
| | | | | | | | | | | | | monitors the entropy data harvested by crypto drivers to verify it complies with FIPS 140-2. If data fails any test then the driver discards it and commences continuous testing of harvested data until it is deemed ok. Results are collected in a statistics block and, optionally, reported on the console. In normal use the overhead associated with this driver is not noticeable. Note that drivers must (currently) be compiled specially to enable use. Obtained from: original code by Jason L. Wright
* o add crypto driver glue for using the new rndtest driver/module; this issam2003-03-116-11/+82
| | | | | | conditional in each driver on foo_RNDTEST being defined_ o bring HIFN_DEBUG and UBSEC_DEBUG out to be visible options; they control the debugging printfs that are set with hw.foo.debug (e.g. hw.hifn.debug)
* Trim an extra blank line that snuck into the last commit.jhb2003-03-111-1/+0
|
* gack; revert previous commit; not only did I read things backward butsam2003-03-111-1/+1
| | | | I was in the wrong tree
* sync with current: reduce default maxbatch setting from 5 to 1sam2003-03-111-1/+1
| | | | Reviewed by: re (sort of, consider this part of my previous request)
* Rename vfs_stdsync function to vfs_stdnosync which matches morekan2003-03-1115-109/+70
| | | | | | | | | | | | | closely what function is really doing. Update all existing consumers to use the new name. Introduce a new vfs_stdsync function, which iterates over mount point's vnodes and call FSYNC on each one of them in turn. Make nwfs and smbfs use this new function instead of rolling their own identical sync implementations. Reviewed by: jeff
* - Change witness_displaydescendants() to accept the indentation level asjhb2003-03-111-21/+25
| | | | | | | | | | | | | | | | | | | | a parameter instead of using the level of a given witness. When recursing, pass an indent level of indent + 1. - Make use of the information witness_levelall() provides in witness_display_list() to use an O(n) algorithm instead of an O(n^2) algo to decide which witnesses to display hierarchies from. Basically, we only display a hierarchy for witnesses with a level of 0. - Add a new per-witness flag that is reset at the start of witness_display() for all witness's and is set the first time a witness is displayed in witness_displaydescendants(). If a witness is encountered more than once in the lock order tree (which happens often), witness_displaydescendants() marks the later occurrences with the string "(already displayed)" and doesn't display the subtree under that witness. This avoids duplicating large amounts of the lock order tree in the 'show witness' output in DDB. All these changes serve to make 'show witness' a lot more readable and useful than it was previously.
* - Split the itismychild() function into two functions: insertchild()jhb2003-03-111-42/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | adds a witness to the child list of a parent witness. rebalancetree() runs through the entire tree removing direct descendants of witnesses who already have said child witness as an indirect descendant through another direct descendant. itismychild() now calls insertchild() followed by rebalancetree() and no longer needs the evil hack of having static recursed variable. - Add a function reparentchildren() that adds all the direct descendants of one witness as direct descendants of another witness. - Change the return value of itismychild() and similar functions so that they return 0 in the case of failure due to lack of resources instead of 1. This makes the return value more intuitive. - Check the return value of itismychild() when defining the static lock order in witness_initialize(). - Don't try to setup a lock instance in witness_lock() if itismychild() fails. Witness is hosed anyways so no need to do any more witness related activity at that point. It also makes the code flow easier to understand. - Add a new depart() function as the opposite of enroll(). When the reference count of a witness drops to 0 in witness_destroy(), this function is called on that witness. First, it runs through the lock order tree using reparentchildren() to reparent direct descendants of the departing witness to each of the witness' parents in the tree. Next, it releases it's own child list and other associated resources. Finally it calls rebalanacetree() to rebalance the lock order tree. - Sort function prototypes into something closer to alphabetical order. As a result of these changes, there should no longer be 'dead' witnesses in the order tree, and repeatedly loading and unloading a module should no longer exhaust witness of its internal resources. Inspired by: gallatin
* Trim useless "../" leading strings from filenames passed into witness.jhb2003-03-111-0/+18
|
* Adjust style of #ifdef's and #endif's to be more consistent and in linejhb2003-03-111-7/+7
| | | | with recent additions to style(9).
* Do the lock order check skip for the LOP_TRYLOCK case after the check forjhb2003-03-111-8/+8
| | | | | | | | recursing on a lock instead of before. This fixes a bug where WITNESS could get a little confused if you did an sx_tryslock() on a sx lock that you already had an slock on. WITNESS would still function correctly but it could result in weirdness in the output of 'show locks'. This also makes it possible for mtx_trylock() to recurse on a lock.
* Rework the eventhandler locking for hopefully the last time. The schemejhb2003-03-112-84/+170
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | used popped into my head during my morning commute a few weeks ago, but it is also very similar (though a bit simpler) to a patch that mini@ developed a while ago. Basically, each eventhandler list has a mutex and a run count. During an eventhandler invocation, the mutex is held while we traverse the list but is dropped while we execute actual handlers. Also, a runcount counter is incremented at the start of an invocation and decremented at the end of an invocation. Adding to the list is not a big deal since the reference of a thread currently executing the handlers remains valid across an add operation. Whether or not new handlers are executed by threads currently executing the handlers for a given list is indeterminate however. The harder case is when a handler is removed from the list. If the runcount is zero, the handler is simply removed from the list directly. If the runcount is not zero, then another thread is currently executing the handlers of this list, so the priority of this handler is set to a magic value (currently -1) to mark it as dead. Dead handlers are not executed during an invocation. If the runcount is zero after it is decremented at the end of an invocation, then a new eventhandler_prune_list() function is called to remove dead handlers from the list. Additional minor notes: - All the common parts of EVENTHANDLER_INVOKE() and EVENTHANDLER_FAST_INVOKE() have been merged into a common _EVENTHANDLER_INVOKE() macro to reduce duplication and ease maintenance. - KTR logging for eventhandlers is now available via the KTR_EVH mask. - The global eventhander_mutex is no longer recursive. Tested by: scottl (SMP i386)
* Retire the KTR_LOCKMGR bit and use it to log eventhandler messagesjhb2003-03-111-1/+1
| | | | instead as KTR_EVH.
* Axe the useless MTX_SLEEPABLE flag. mutexes are not sleepable locks.jhb2003-03-113-7/+2
| | | | | Nothing used this flag and WITNESS would have panic'd during mtx_init() if anything had.
* Use a shorter and less redundant name for the sysctl tree lock.jhb2003-03-111-1/+1
|
* Use the KTR_LOCK mask for logging events via KTR in lockmgr() ratherjhb2003-03-111-4/+4
| | | | than KTR_LOCKMGR. lockmgr locks are locks just like other locks.
* Trim leading "../" sequences from filenames.jhb2003-03-111-0/+3
|
* Use bus_space_handle_t to represent host port and virtual addresses;jake2003-03-113-36/+36
| | | | | | bus_addr_t may not be appropriate. Sponsored by: DARPA, Network Associates Laboratories
* FIPS 140-2 rng data tester for h/w crypto devices. This driver periodicallysam2003-03-113-0/+10
| | | | | | | | | | | | | monitors the entropy data harvested by crypto drivers to verify it complies with FIPS 140-2. If data fails any test then the driver discards it and commences continuous testing of harvested data until it is deemed ok. Results are collected in a statistics block and, optionally, reported on the console. In normal use the overhead associated with this driver is not noticeable. Note that drivers must (currently) be compiled specially to enable use. Obtained from: original code by Jason L. Wright
* correct output byte count statistic collectionsam2003-03-111-2/+3
|
* Remove bogus UNLOCK in if_wi.c. Since we no longer WILOCK() in theimp2003-03-111-3/+1
| | | | | | | | attach routine, calling WIUNLOCK in the error case of one of the ifs for that routine is now bogus. This should have been removed when the WILOCK() was removed, but wasn't. Submitted by: "Harti Brandt" <brandt@fokus.fraunhofer.de>
* Add _HID of IrDA module and Pen tablet ontakawata2003-03-111-0/+2
| | | | | | Tablet PC Acer Travel Mate C100. Sponsored by: ACER ,Alpha Omega, MYCOM , Synnex
* FreeBSD 5.0 has stopped shipping /modules 2.5 years ago. Catchru2003-03-111-1/+1
| | | | | up with this further by excluding /modules from the (default) kern.module_path.
* Make uhci_waitintr() robust to interrupts being enabled, even thoughiedowse2003-03-111-4/+3
| | | | | | | | | it is expected that they will not be enabled at the time that it is called. This is reported to work around a problem in RELENG_4 where the kernel panics on boot if FAST_IPSEC and crypto support are enabled. Tested by: Scott Johnson <scottj@insane.com>
* - Regularize variable usage in cluster_read().jeff2003-03-111-92/+62
| | | | | | | | | - Issue the io that we will later block on prior to doing cluster read ahead so that it is more likely to be ready when we block. - Loop issuing clustered reads until we've exhausted the seq count supplied by the file system. - Use a sysctl tunable "vfs.read_max" to determine the maximum number of blocks that we'll read ahead.
* Lock proc lock before changing p_flag.davidxu2003-03-112-0/+4
|
* Fix signal delivering bug for threaded process.davidxu2003-03-113-14/+16
|
* Quirk for SanDisk ImageMate II compact flash readernjl2003-03-111-0/+8
| | | | | | PR: kern/47877 Submitted by: Mike Durian <durian@boogie.com> MFC after: 3 days
* Quirk for Pentax Optio 230 USB camera. Note that other products probablynjl2003-03-112-0/+14
| | | | | | | | | use the underlying AsahiOptical USB chip and thus this quirk may need to be generalized in the future. PR: kern/46369 Submitted by: Tim Vanderhoek <vanderh@ecf.utoronto.ca> MFC After: 3 days
* usbdevs entry for Asahi Optical OPTIO 230 digital camera. Regen.njl2003-03-113-0/+12
|
* Update Radeon PCI IDs and naming from pciids.sf.net.anholt2003-03-111-26/+28
|
* Fix threaded process job control bug. SMP tested.davidxu2003-03-115-84/+68
| | | | Reviewed by: julian
* If we run out of consumers while orphaning them, and the provider's geomphk2003-03-101-0/+5
| | | | | | is withering, destroy the provider when done. This was exposed by the recent change to geom_dev's orphaning logic.
* Fix yet another fallout of our M_* song and dance.phk2003-03-101-1/+1
|
* "Or" is expressed with 2 separate config lines.jake2003-03-101-1/+2
| | | | Reported by: Stijn Hoop <stijn@win.tue.nl>
* Remove trainling whitespace.kan2003-03-102-21/+20
|
* PHCC[1]:phk2003-03-102-4/+4
| | | | | | | | | | I had commented the #ifdef INVARIANTS checks out to make sure I ran this code in all kernels and forgot to comment the #ifdefs back in before I committed. Spotted by: bmilekic [1] PHCC = Pointy Hat Correction Commit
* Make malloc and mbuf allocation mode flags nonoverlapping.phk2003-03-104-7/+39
| | | | | | Under INVARIANTS whine if we get incompatible flags. Submitted by: imp
* Now that we have WITNESS_WARN(), we only call witness_list() from thejhb2003-03-101-41/+29
| | | | | | | | | ddb 'show locks' command. Thus, move witness_list() to the #ifdef DDB section and remove extra checks for calling this function outside of DDB. Also, witness_list() now returns void instead of returning an int. Reported by: Steve Ames <steve@energistic.com> Prodded by: davidxu
* Remove the enclose_print() call, it is already called from ata-disk.csos2003-03-101-1/+0
|
* Dont use r_bmio on Cyrix chips if not set from BIOS.sos2003-03-101-2/+5
|
* Fix two rounds of breakages and cleanup. Remove the sccdebug sysctlmarcel2003-03-101-55/+11
| | | | | | while I'm here and garbage collect dead code (ssc_clone). Define d_maxsize as DFLTPHYS for now because that's what it will be if we don't define it.
* Add a a sysctl, hw.kbd.keymap_restrict_change, which acts a bitdwmalone2003-03-091-0/+144
| | | | | | | | | | | | | | | | | | | | | like secure level but which restricts changes to the keymap. Its values impose the following restrictions: 0: No restriction - this is the default. 1: Only root can change restricted keys (like boot, panic, ...) 2: Only root can change restricted keys and regular keys. Other users still can change accents and function keys. 3: Only root can change restricted keys, regular keys and accents. 4: Only root can change any of the keymap (restricted keys, regular keys, accents and function keys). Unfortunately, the keyboard's accent map is cleared when a new keymap is loaded, which makes the distinction between level 3 and level 4 less useful. The MAC guys might like to make this a policy? No objections from: -audit about 6 moths ago
* Don't call make_dev() before we are ready for it.phk2003-03-091-1/+9
|
* Remove some unnecessary actions by the zero-copy setup and teardown code.alc2003-03-091-10/+1
| | | | | | | | | Remove an incorrect comment. (Incrementing an object's reference count does not prevent a process from exiting. The real concern here is that the physical page must not be deleted until transmission is complete. That is already handled by the VM system and sf_buf_free().) Tested by: ken
* Fix device freeze to reduce output packet size.akiyama2003-03-094-5/+39
| | | | And make this value configurable by kernel config or sysctl.
* Fix page fault with FTDI's USB serial device.akiyama2003-03-091-4/+23
| | | | | Fix lost characters counting. Move setting receiver state to proper place on ucomstopread().
* Fix duplicate sc_dying usage.akiyama2003-03-092-13/+8
| | | | | All drivers which depend on ucom interfaces should use only one sc_dying.
OpenPOWER on IntegriCloud