summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Release the hold on ata_delayed_attach earlier so we can use tsleepsos2004-09-091-6/+7
| | | | | | in the boot probe as well. Suggested by: gibbs
* Check flag do_bridge always, even if kernel was compiled withoutglebius2004-09-091-11/+5
| | | | | | | | BRIDGE support. This makes dynamic bridge.ko working. Reviewed by: sam Approved by: julian (mentor) MFC after: 1 week
* Do not call xl_init_locked() unconditionally when we are bringed UP. Callglebius2004-09-091-2/+3
| | | | | | | | | | | it only if we weren't UP before. In some cases xl_init causes long media re-negotiation, and ppp(8) fails to open PPPoE connection because it sets IFF_UP every time before opening PPPoE connection. PR: kern/69133 Patch by: mdodd Approved by: wpaul, julian (mentor) MFC after: 1 week
* bump .Ddalfred2004-09-091-1/+1
| | | | requested by: ru
* The disk labels generated by bsdlabel can no address more thanbrooks2004-09-092-7/+22
| | | | | | | | | | | 0xffffffff sectors. Document this limit and avoid installing bogus labels on disks with more sectors. Allowing the installation of labels addressing as much of the disk as possiable may be a useful addition in some situations, but this was easy to implement and should reduce confusion. PR: bin/71408
* Hard code witness lock order for BPF locks.rwatson2004-09-091-0/+7
|
* Reformulate bpf_dettachd() to acquire the BIF_LOCK() as well asrwatson2004-09-091-11/+20
| | | | | | | | | | | | | BPFD_LOCK() when removing a descriptor from an interface descriptor list. Hold both over the operation, and do a better job at maintaining the invariant that you can't find partially connected descriptors on an active interface descriptor list. This appears to close a race that resulted in the kernel performing a NULL pointer dereference when BPF sessions are detached during heavy network activity on SMP systems. RELENG_5 candidate.
* Plug an fd leak by using autoh_freeall(3).alfred2004-09-091-8/+36
| | | | | | | Refuse to run unless root. Check in /etc, /usr/local/etc and ./ for the "autotab" configuration file. Add more debug statements.
* Add/document autoreq_getxid(3), which gets the autofs requestalfred2004-09-093-5/+22
| | | | | | | | | transaction id from the request, this is useful for debugging. Fix the autoh_freeall(3) function to properly free the array of auto handles. Before it was freeing individual members of the list OK, however it was then advancing the pointer and freeing the wrong data for the whole list.
* Reformulate use of linked lists in 'struct bpf_d' and 'struct bpf_if'rwatson2004-09-092-38/+24
| | | | | | | | | | | | to use queue(3) list macros rather than hand-crafted lists. While here, move to doubly linked lists to eliminate iterating lists in order to remove entries. This change simplifies and clarifies the list logic in the BPF descriptor code as a first step towards revising the locking strategy. RELENG_5 candidate. Reviewed by: fenner
* Compare/set pointers using NULL not 0.rwatson2004-09-091-3/+3
|
* add support for documented readonly option...jmg2004-09-081-1/+5
| | | | | | | also print out the option that is unknow so that the user knows what (s)he did wrong.. MFC after: 3 days
* Remove debug output.alfred2004-09-081-4/+4
|
* Fix a .Fn that should be an .Fa.alfred2004-09-081-3/+16
| | | | | Clear up the spelling and language when describing how to select/poll for an autofs event.
* Clean up rev 1.49 by using the temperature conversion for _PSV also andnjl2004-09-081-4/+5
| | | | wrap a long line.
* Use atomic ops in pmap_clear_ptes() to prevent SMP races that couldalc2004-09-082-7/+20
| | | | | | | | result in the loss of an accessed or modified bit from the pte. In collaboration with: tegge@ MT5 candidate
* Do not compile in zlib.c. Add a dependency on module instead.fjoe2004-09-082-2/+3
|
* Show current status of mirror device directly.pjd2004-09-081-0/+9
| | | | Suggested by: Krzysztof CiepĀ³ucha <kris@home.pl>
* Make the output more suitable for use in a frameset.des2004-09-081-24/+24
|
* Reduce the size of struct defid's defid_dirclust, defid_dirofs andtjr2004-09-081-3/+3
| | | | | | | | | (disabled) defid_gen members from u_long to u_int32_t so that alignment requirements don't cause the structure to become larger than struct fid on LP64 platforms. This fixes NFS exports of msdos filesystems on at least amd64. PR: 71173
* Back out v1.24. v1.40 of sys/sparc64/sparc64/bus_machdep.c fixes thekensmith2004-09-081-3/+1
| | | | | | problem this hack was put in place for. MFC to be done if the fix to bus_machdep.c is MFC-ed.
* Merge from NetBSD:tjr2004-09-081-3/+18
| | | | | | | | | | | | | | Fix a problem in previous: we can't blindly assume that we have wincnt entries available at the offset the file has been found. If the dos directory entry is not preceded by appropriate number of long name entries (happens e.g. when the filesystem is corrupted, or when the filename complies to DOS rules and doesn't use any long name entry), we would overwrite random directory entries. There are still some problems, the whole thing has to be revisited and solved right. Submitted by: Xin LI
* Merge from NetBSD:tjr2004-09-081-0/+5
| | | | | | | | | | Fix a panic that occurred when trying to traverse a corrupt msdosfs filesystem. With this particular corruption, the code in pcbmap() would compute an offset into an array that was way out of bounds, so check the bounds before trying to access and return an error if the offset would be out of bounds. Submitted by: Xin LI
* sync with private code:alfred2004-09-0811-12/+17
| | | | | fix a 5.x'ism that 4.x needs protection from. make this code compile standalone.
* Fixed sound-related hints. (Yes, this is ambiguous but matches reality.)ru2004-09-081-14/+14
| | | | | Reviewed by: matk, cg (an earlier version) MT5 after: 3 days
* Update sound-related manpages to account for the recent change inru2004-09-0820-444/+74
| | | | | | | | | | | | | | | | | | | | | | | | device and module naming. The following files were repo-copied: csa.4 -> snd_csa.4 gusc.4 -> snd_gusc.4 maestro3.4 -> snd_maestro3.4 sbc.4 -> snd_sbc.4 uaudio.4 -> snd_uaudio.4 The pcm(4) manpage wasn't renamed to sound(4) as there are nearby plans to rename "device sound" to "device snd", to address the ambiguity in naming, so pcm.4 is linked to sound.4 for the moment. (We also mumble something about the future plans in the manpage.) Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now have their own snd_*.4 manpages. Fixes for recent snd_*.4 manpages: added missing "device sound" to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>" in most cases). MT5 after: 3 days
* Fix/clean up return values checking.pjd2004-09-084-31/+31
|
* Back out 1.88.imp2004-09-081-9/+11
| | | | | | | | | | | | | The reference counts are there to block detach until the sleepers in read/write/ioctl have gotten out, not to prevent the open device from going away. Restore the old behavior so that we have a chance to wake up sleepers when the usb device goes away, so they can properly return EIO back to the caller when this happens. Otherwise, we have a guarnateed panic waiting to happen when a device detaches with an active read channel. This should be merged to 5 asap.
* Correct a typo in a comment.ru2004-09-081-1/+1
| | | | Submitted by: Xin LI
* Fix a problem with tag->boundary inheritence that has existed since day onescottl2004-09-087-38/+35
| | | | | | | | | | | | | | and was propagated to nearly every platform. The boundary of the child needs to consider the boundary of the parent and pick the minimum of the two, not the maximum. However, if either is 0 then pick the appropriate one. This bug was exposed by a recent change to ATA, which should now be fixed by this change. The alignment and maxsegsz tag attributes likely also need a similar review in the near future. This is a MT5 candidate. Reviewed by: marcel Submitted by: sos (in part)
* Re-add ifi_epoch, to struct if_data, this time replacing ifi_unusedbrooks2004-09-083-2/+6
| | | | | | | | | | | | to avoid ABI changes. It is set to the last time the interface counters were zeroed, currently the time if_attach() was called. It is intentended to be a valid value for RFC2233's ifCounterDiscontinuityTime and to make it easier for applications to verify that the interface they find at a given index is the one that was there last time they looked. Due to space constraints ifi_epoch is a time_t rather then a struct timeval. SNMP would prefer higher precision, but this unlikely to be useful in practice.
* Sync the busdma code with i386. The most tangible upshot is thatmarcel2004-09-081-207/+153
| | | | | | | | | | | the alignment and boundary constraints are being respected, which fixes the reported ATA problems with SiI chips. I consider the busdma implementation worrisome nonetheless. Not only is there too much MI code duplicated in MD files, there's a lot of questionable code. I smell a wholesale, cross-platform overhaul coming... MT5 candidate.
* Remove vinum from the list. I no longer have the time and energy togrog2004-09-081-1/+0
| | | | even review changes.
* We don't need device counts anymore. Also remove device.hints entriesbrueffer2004-09-081-5/+1
| | | | | | for ie1, to be in line with the other manpages. MFC after: 3 days
* We don't need device counts anymorebrueffer2004-09-081-1/+1
| | | | MFC after: 3 days
* Fix a cut-n-paste glitch with SCHED_4BSD.scottl2004-09-071-1/+1
|
* Switch the default scheduler to 4BSD to match what will go into RELENG_5 soon.scottl2004-09-075-5/+15
| | | | | | | It can be switched back once 5.3 is tested and released. Also turn on PREEMPTION as many of the stability problems with it have been fixed. MT5: 3 days.
* - Remove listing for NCR5380/NCR53400 and UltraStor 14F/24F/3F4;simon2004-09-072-148/+8
| | | | | | | | | | | the drivers were removed over 5 years ago. - Note that WD7000 is supported by the wds(4) driver and move it to the generic SCSI section, since it was converted to CAM some time ago. - Remove section about non-CAM drivers, since there are none left in the section. - Autogenerate device listing for ct(4). MFC after: 2 days
* new version of cryptotest (w/ only code from me)sam2004-09-072-1/+583
| | | | Reviewed by: imp
* Don't change the state of the system in acpi_tz_establish(). Before, wenjl2004-09-071-16/+22
| | | | | | | | | | | | | | would turn off all fans when initializing a zone. However, the HP Omnibook 500 generates a notify saying the zone needs to be re-evaluated whenever its fan is switched on or off. This produced an infinite loop. Also, note that running _SCP can generate the same notify. Since we need to make sure old fan references are turned off when getting new ones, run acpi_tz_monitor() first. This will turn off any unneeded fans. Then, check for new settings. After that, run acpi_tz_monitor() again to turn on/off any fans referenced by the new settings. Tested by: brooks
* Instead of trusting _STA from power resources, cache the first valuenjl2004-09-071-5/+11
| | | | | | | returned and then infer the state from calls to _ON/_OFF. This works around a problem in systems that don't correctly report the state (i.e. the HP Omnibook 500 reports "on" for its fan always after it has been turned on once).
* Mark bundle as unused in case we're compiled with NORADIUS.phk2004-09-071-3/+3
|
* [[ Forced commit due to fumble with the file used to commit with.imp2004-09-070-0/+0
| | | | | | | | | | | | | | | cvsgNMRSs vs cvsg4JFe3 :-( ]] When recursing, print the target name as well as the subdirectory. This changes the output a little, but appears to break no scripts. These changes should make the debugging of build problems easier, as well as explain why it appears things build 4 times (they don't, really, since there's obj, depend, all and install). I've been running these changes, or variations on them, for about 2 years. Reviewed by: arch@ (des, markm, koshy, marcel, scottl)
* Although 'Unanimous Consent' appears to be a well defined and used inimp2004-09-072-11/+11
| | | | | | | | | | | | | | | the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
* Document the following knobs: CD_EXTRA_BITS, EXTRA_SRC, HTTP_PROXYru2004-09-071-1/+14
| | | | | | | and FTP_PROXY. Removed bitrot (BOOT_CONFIG). PR: misc/71465 Submitted by: Jon Passki <cykyc@yahoo.com>
* Improve markup and language.dd2004-09-071-1/+3
|
* Create simple function init_va_filerev() for initializing a va_filerevphk2004-09-076-93/+19
| | | | | | | | | field. Replace three instances of longhaired initialization va_filerev fields. Added XXX comment wondering why we don't use random bits instead of uptime of the system for this purpose.
* Explicitly pass vnode to nfs_doio() and mountpoint to nfs_asyncio().phk2004-09-075-26/+17
|
* Explicitly pass vnode to smbfs_doio() function.phk2004-09-073-6/+3
|
* Explicitly pass the vnode to the nw_doio() function.phk2004-09-073-7/+4
|
OpenPOWER on IntegriCloud