summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Added whiteout behavior option. ``-o whiteout=always'' is default modedaichi2007-10-143-2/+32
| | | | | | | | | | | (it is established practice) and ``-o whiteout=whenneeded'' is less disk-space using mode especially for resource restricted environments like embedded environments. (Contributed by Ed Schouten. Thanks) Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Default copy mode has been changed from traditional-mode to transparent-mode.daichi2007-10-141-1/+1
| | | | | | | | | | | Some folks who have reported some issues have solved with transparent mode. We guess it is time to change the default copy mode. The transparent-mode is the best in most situations. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Fixed un-vrele issue of upper layer root vnode of unionfs.daichi2007-10-141-1/+1
| | | | | | | Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Added NULL check code pointed out by Coverity. (via Stanislavdaichi2007-10-141-0/+2
| | | | | | | | | Sedov. Thanks) Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* - It has been become MPSAFE.daichi2007-10-142-22/+51
| | | | | | | | | | | - Fixed lock panic issue under MPSAFE. - Fixed panic issue whenever it locks vnode with reclaim. - Fixed lock implementations not conforming to vnode_if.src style. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Fixed vnode unlock/vrele untreated issues whenever errors havedaichi2007-10-141-4/+4
| | | | | | | | | occurred during some treatments. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* - Added support for vfs_cache on unionfs. As a result, you can usedaichi2007-10-143-171/+43
| | | | | | | | | | | | | applications that use procfs on unionfs. - Removed unionfs internal cache mechanism because it has vfs_cache support instead. As a result, it just simplified code of unionfs. - Fixed kern/111262 issue. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Added treatments to prevent readdir infinity loop using with Linux binarydaichi2007-10-141-29/+23
| | | | | | | | | compatibility feature. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Changed it frees unneeded memory ASAP.daichi2007-10-141-1/+5
| | | | | | | Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Log:daichi2007-10-141-0/+6
| | | | | | | | | Improved access permission check treatments. Submitted by: Masanori Ozawa <ozawa@ongs.co.jp> (unionfs developer) Reviewed by: jeff, kensmith Approved by: re (kensmith) MFC after: 1 week
* Convert coretemp(4) to the hardware sensors framework andnetchild2007-10-141-34/+45
| | | | | | | | | | make sure to never call sched_bind() for uninitialised CPUs. Submitted by: Constantine A. Murenin <cnst@FreeBSD.org> Sponsored by: Google Summer of Code 2007 (GSoC2007/cnst-sensors) Mentored by: syrinx Tested by: many OKed by: kensmith
* Import it(4) and lm(4), supporting most popular Super I/O Hardware Monitors.netchild2007-10-1413-0/+1803
| | | | | | | | | Submitted by: Constantine A. Murenin <cnst@FreeBSD.org> Sponsored by: Google Summer of Code 2007 (GSoC2007/cnst-sensors) Mentored by: syrinx Tested by: many OKed by: kensmith Obtained from: OpenBSD (parts)
* Import OpenBSD's sysctl hardware sensors framework.netchild2007-10-144-1/+594
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit includes the following core components: * sample configuration file for sensorsd * rc(8) script and glue code for sensorsd(8) * sysctl(3) doc fixes for CTL_HW tree * sysctl(3) documentation for hardware sensors * sysctl(8) documentation for hardware sensors * support for the sensor structure for sysctl(8) * rc.conf(5) documentation for starting sensorsd(8) * sensor_attach(9) et al documentation * /sys/kern/kern_sensors.c o sensor_attach(9) API for drivers to register ksensors o sensor_task_register(9) API for the update task o sysctl(3) glue code o hw.sensors shadow tree for sysctl(8) internal magic * <sys/sensors.h> * HW_SENSORS definition for <sys/sysctl.h> * sensors display for systat(1), including documentation * sensorsd(8) and all applicable documentation The userland part of the framework is entirely source-code compatible with OpenBSD 4.1, 4.2 and -current as of today. All sensor readings can be viewed with `sysctl hw.sensors`, monitored in semi-realtime with `systat -sensors` and also logged with `sensorsd`. Submitted by: Constantine A. Murenin <cnst@FreeBSD.org> Sponsored by: Google Summer of Code 2007 (GSoC2007/cnst-sensors) Mentored by: syrinx Tested by: many OKed by: kensmith Obtained from: OpenBSD (parts)
* Split ng_pppoe_rcvdata() function into three hook-specific onesmav2007-10-141-464/+465
| | | | to simplify code and reduce stack usage.
* Remove ng_pppoe_sendpacket() function to simplify code as it is calledmav2007-10-141-79/+39
| | | | as much times as it has cases inside of it.
* Print the ZFS ereport to the console if vfs.zfs.debug is set to help diagnosethompsa2007-10-142-0/+2
| | | | | | problems with zfs-on-root since devd isnt running yet. Reviewed by: pjd
* revert 1.18: the negotiated rate set may not match the halsam2007-10-131-18/+34
| | | | | | | rate tables, so using the hal's rateCodeToIndex array will produce wrong indices for the negotiated rate set MFC after: 3 days
* Rewrite puc_pci_match() to handle non-trivial cases correctly.des2007-10-131-14/+19
| | | | MFC after: 1 week
* Do not use __XSCALE__ to detect if clz is available, use _ARM_ARCH_5 instead.cognet2007-10-131-1/+1
| | | | MFC After: 3 days
* Do not use __XSCALE__ to detect if pld/strd/ldrd is available, usecognet2007-10-135-25/+25
| | | | | | _ARM_ARCH_5E instead. MFC After: 3 days
* Define _ARM_ARCH_5E too, so that we know if pld/strd/ldrd are available.cognet2007-10-131-1/+6
| | | | MFC After: 3 days
* I don't know what I was smoking when I wrote these three years ago; thedes2007-10-132-6/+22
| | | | | | return value is an error code, hence always an int. While I'm here, add getenv_uint() for completeness.
* Add NOP-message polling to ciss_periodic().iwasaki2007-10-131-1/+80
| | | | | | | | Disable adapter by detecting adapter is dead. Tested by: Masaki YATSU(on RELENG_6) Reviewed by: scottl MFC after: 1 week
* Fix a NULL pointer dereference in Tx checksum calculation.yongari2007-10-131-0/+5
| | | | Pointed out by: marius
* Add definitions for the 3rd ATA support word.scottl2007-10-121-0/+9
|
* Add a bunch of definitions and structures to support newer drivers.scottl2007-10-121-1/+110
|
* The ukbd driver has some questionable "magic" to for a default keyboardjhb2007-10-121-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | which is ukbd0. Specifically, the keyboard driver structures for ukbd0 are not allocated/freed but are statically allocated via a persistent global variable. There is some additional magic for the ukbd0 such that if the keyboard is marked as probed in this global variable, then we don't check to see if the device_t we are probing has an interface. This causes a problem if an attach of ukbd0 fails without fulling clearing the state in the global variable. Specifically, if the keyboard fails to initialize in init_keyboard() or kbd_register(), then the keyboard will still be marked as probed. The USB layer will then try to offer the "generic" version of the USB keyboard device (as opposed to the per-interface sub-devices) and the ukbd(4) driver will see that the keyboard is marked probe and will skip the "is this a per-interface device" check. Later in ukbd_attach() it panics because it tries to dereference the interface pointer which is NULL. The fix is to clear the flags in the persistent keyboard data for ukbd0 when init_keyboard() or kbd_register() fail. MFC after: 1 week Reviewed by: imp
* NFS MP scaling changes.mohans2007-10-124-75/+131
| | | | | | | | | | | | | | - Eliminate the hideous nfs_sndlock that serialized NFS/TCP request senders thru the sndlock. - Institute a new nfs_connectlock that serializes NFS/TCP reconnects. Add logic to wait for pending request senders to finish sending before reconnecting. Dial down the sb_timeo for NFS/TCP sockets to 1 sec. - Break out the nfs xid manipulation under a new nfs xid lock, rather than over loading the nfs request lock for this purpose. - Fix some of the locking in nfs_request. Many thanks to Kris Kennaway for his help with this and for initiating the MP scaling analysis and work. Kris also tested this patch thorougly. Approved by: re@ (Ken Smith)
* Do not attempt to make an NFS rpc call if using tftpps2007-10-122-0/+9
| | | | | PR: kern/91720 Submitted by: Ruben Kerkhof
* Fix a mistake made in the MPSAFE commit that caused CAM to serialize requestsscottl2007-10-121-1/+2
| | | | to the controller.
* For some blasted reason the SATA WC change frees a structure right in thescottl2007-10-121-1/+0
| | | | middle of using it.
* Play better with CAM so that there aren't so many spurious warnings at boot.scottl2007-10-121-17/+14
|
* Deferred interrupts don't work yet, disable them.scottl2007-10-121-0/+2
| | | | Submitted by: Manjunath Ranganathaiah
* - Change the wakeup logic associated with having multiple sleeperscsjp2007-10-121-2/+2
| | | | | | | | | | | | | | | | on multiple different audit pipes. The old method used cv_signal() which would result in only one thread being woken up after we appended a record to it's queue. This resulted in un-timely wake-ups when processing audit records real-time. - Assign PSOCK priority to threads that have been sleeping on a read(2). This is the same priority threads are woken up with when they select(2) or poll(2). This yields fairness between various forms of sleep on the audit pipes. Obtained from: TrustedBSD Project Discussed with: rwatson MFC after: 1 week
* Make sure that we refresh the PID on read(2) and write(2) operations.csjp2007-10-121-0/+2
| | | | | | | | | | | | | This fixes the process portion of the bpf(4) stats if the peer forks into the background after it's opened the descriptor. This bug results in the following behavior for netstat -B: # netstat -B Pid Netif Flags Recv Drop Match Sblen Hblen Command netstat: kern.proc.pid failed: No such process 78023 em0 p--s-- 2237404 43119 2237404 13986 0 ?????? MFC after: 1 week
* Remove unneeded debug printf that is broken on 64bit arches.thompsa2007-10-121-1/+1
|
* Add another zydas device: Planex GW-US54GD (a.k.a Dempaotoko)takawata2007-10-122-0/+2
|
* Bring in some new Sierra Wireless drivers running under pccard.remko2007-10-122-0/+40
| | | | | | | | | | (AC710/AC750/AC850/A550/A555/A710/A750) PR: kern/110190 Submitted by: Pascal Vizeli<pvizeli at yahoo dot de> Approved by: imp (mentor) MFC After: 1 week
* Spelling fix for interupt -> interruptkevlo2007-10-1229-41/+41
|
* Update ipw to work with the new net80211 stack, plus other driver improvements.thompsa2007-10-123-219/+868
| | | | | | | | | | | | | - Add proper scanning support rather than letting the firmware grab the first access point - Overhaul state changes - Use macros for locking and provide _locked() versions of some functions - Increase debugging output - Use a callout rather than the old watchdog interface - Improve style, function names and defines - Add WPA (TKIP) support Based heavily on a patchset provided by Sam Leffler.
* Protect struct seq with mutex.mav2007-10-121-17/+72
| | | | Approved by: glebius (mentor)
* Remove one unneded assertion. It is also checked inmav2007-10-121-5/+0
| | | | | | ng_l2tp_seq_check(). Approved by: glebius (mentor)
* Replace single rcvdata with 3 distinct to simplify code andmav2007-10-121-74/+77
| | | | | | reduce stack usage. Approved by: mentor (glebius)
* Remove duplicate variables.mav2007-10-121-11/+3
|
* Set the NFS server sockbuf high watermarks to the system defaultsmohans2007-10-122-6/+5
| | | | | | | (up form 32KB). The low highwatermark setting caused UDP fullsock request drops, throttling thruput greatly. Reported by: Kris Kennaway Approved by: re@ (Ken Smith)
* Not all VIA Rhine chips support 256 register space. So touchingyongari2007-10-122-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VR_STICKHW register would result in unexpected results on these hardwares. wpaul said the following for the issue. The vr_attach() routine unconditionally does this for all supported chips: /* * Windows may put the chip in suspend mode when it * shuts down. Be sure to kick it in the head to wake it * up again. */ VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1)); The problem is, the VR_STICKHW register is not valid on all Rhine devices. The VT86C100A chip, which is present on the D-Link DFE-530TX boards, doesn't support power management, and its register space is only 128 bytes wide. The VR_STICKHW register offset falls outside this range. This may go unnoticed in most scenarios, but if you happen to have another PCI device in your system which is assigned the register space immediately after that of the Rhine, the vr(4) driver will incorrectly stomp it. In my case, the BIOS on my test board decided to put the register space for my PRO/100 ethernet board right next to the Rhine, and the Rhine driver ended up clobbering the IMR register of the PRO/100 device. (Long story short: the board kept locking up on boot. Took me the better part of the morning suss out why.) The strictly correct thing to do would be to check the PCI config space to make sure the device supports the power management capability and only write to the VR_STICKHW register if it does. Instead of inspecting chip revision numbers for the availability of VR_STICKHW register, check the existence of power management capability of the hardware as wpaul suggested. Reported by: wpaul Suggested by: wpaul OK'ed by: jhb
* Fix two panics in lagg.thompsa2007-10-122-36/+34
| | | | | | | | | | | | | 1. The locking was changed to shared but roundrobin mode still updated a pointer in the softc with the next tx interface to use. This will panic under high load. Change this to an atomically incremented sequence number in order to choose the tx port in round robin. 2. IFQ_HANDOFF will free the mbuf if the queue is full, this will then be freed again by lagg_start() and panic. Reorganised the error handling and freeing to fix this. MFC after: 3 days
* Allow recursion on the 'zones' internal UMA zone.jhb2007-10-111-1/+1
| | | | | | | Submitted by: thompsa MFC after: 1 week Approved by: re (kensmith) Discussed with: jeff
* To honor the birth of RELENG_7 bump HEAD to 8.0-CURRENT.kensmith2007-10-112-2/+2
| | | | Approved by: re (implicit)
* Add PCI ID for ICH9 AHCI w/ two adapters.delphij2007-10-092-0/+2
| | | | | | Tested by: Abdullah Ibn Hamad Al-Marri <almarrie gmail com> Approved by: sos Approved by: re (kensmith)
OpenPOWER on IntegriCloud