summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* s/on a crt//brd2006-05-251-2/+2
| | | | | | | systat is working great on this LCD ;) Submitted by: Ben Haga <tuximus AT absoludicrous DOT com> MFC after: 3 days
* - Add include for libutil.h and string.h for prototype.delphij2006-05-251-1/+3
| | | | | - Cast the rvalue to be compared with the result of strlen() to size_t.
* Do not set B_NOCACHE on buffers when releasing them in flushbuflist().ups2006-05-254-1/+20
| | | | | | | | | | | | | | | If B_NOCACHE is set the pages of vm backed buffers will be invalidated. However clean buffers can be backed by dirty VM pages so invalidating them can lead to data loss. Add support for flush dirty page in the data invalidation function of some network file systems. This fixes data losses during vnode recycling (and other code paths using invalbuf(*,V_SAVE,*,*)) for data written using an mmaped file. Collaborative effort by: jhb@,mohans@,peter@,ps@,ups@ Reviewed by: tegge@ MFC after: 7 days
* Since NFSv4 is not SMP safe, nfsiod needs to acquire Giant for NFSv4 mountsmohans2006-05-242-0/+9
| | | | | | before doing the read/write. Reported by: Chuck Lever.
* When starting up threads in taskqueue_start_threads create themsam2006-05-241-9/+16
| | | | | | | | | | | | stopped before adjusting their priority and setting them on the run q so they cannot race for resources (pointed out by njl). While here add a console printf on thread create fails; otherwise noone may notice (e.g. return value is always 0 and caller has no way to verify). Reviewed by: jhb, scottl MFC after: 2 weeks
* Adjust minimum iod threads from 4 to 0 -- since we compile the NFSrwatson2006-05-241-1/+1
| | | | | | | | | | | | | | | | | client into the kernel by default, and many users won't use NFS, don't start an extra 4 kernel threads that are unused. Once NFS becomes active, it will start nfsiod's as it needs them. We might consider mandating a minimum iod's equal to the number of active NFS mounts (truncated to some value), which would force some to remain available without having to create a new one if the file system is mostly inactive. PR: 70880 MFC after: 2 weeks Prodded by: cel Head nod: peter Pointed out by: Joe <fbsd_user at a1poweruser dot com>
* Export the pribus, secbus and subbus as sysctls for informationimp2006-05-242-20/+31
| | | | purposes only. Additional information may be exported in the future.
* Suspend the children before we turn off card events in hardware. Thisimp2006-05-241-2/+4
| | | | | | | | was done, I believe, to work around some cards having issues in the suspend case. I think that this helped my Sony VAIO TS505 work better when it had certain wireless cards in it and I did a apm -z. I've not tested suspend/resume on other laptops in a long time, so I hope this doesn't cause greif. Please let me know if it does.
* Fix a race when detaching the cbb worker thread. There were a coupleimp2006-05-241-1/+7
| | | | | | of cases where we didn't take out the lock before setting or clearing a bit. This apparently can lead to a race at kldunload time (at least on my Turion64 laptop, never saw it on my Sony Vaio).
* Add cbb, cardbus, pccard and exca to the list of modules. The appearimp2006-05-241-0/+4
| | | | to work on the Turion64 laptop I have.
* Vinod has passed the maintainership for the twa/twe drivers towilko2006-05-241-2/+2
| | | | | | | | | | Adam Radford as follows: twe aradford@amcc.com Pre-commit review requested twa aradford@amcc.com Pre-commit review requested With hat: core-secretary Requested by: vkashyap
* While reviewing NFS client for another PR, noticed this omission in thecel2006-05-241-1/+1
| | | | | | | NFSv4 client READDIR logic. This change matches the logic in the version 2 and 3 code. Sponsored by: Network Appliance, Incorporated
* make cryptotest compile after the latest changes to cryptodev.hmr2006-05-241-3/+3
|
* Forced commit - last checkin got away from me.mjacob2006-05-241-0/+1
| | | | | | | | | | This version of scsi_target.c removes all SMP locking until we have a lock-aware CAM stack. This allows us to use KNOTE without a panic at least. It's not yet clear whether target mode is working yet or not. Discussed with: Scott, Ken, Nate, Justin
* Sorry- last delta was checked in by mistake.mjacob2006-05-241-2/+1
|
* Make physical buffers in cam_periph_mapmem owned by the kernel in case wemjacob2006-05-243-58/+21
| | | | | | | | return to user space w/o waiting for I/O to complete. I tried to get several folks who know this code better than me to review it with no luck. I *do* know that w/o this code, using the SCSI target driver panics in userret (if it doesn't panic in knote first).
* Unnest includes before forthcoming editing.glebius2006-05-2416-20/+95
|
* Workaround a hang on some nForce2 systems that can happen if the CPU goesjhb2006-05-241-0/+38
| | | | | | | into and out of the halt state very quickly. Submitted by: Andriy Gapon <avg at icyb dot net dot ua> MFC after: 1 week
* Revision 1.4 set access for all sensitive files in /proc/<PID> to mode 0ghelmer2006-05-241-3/+6
| | | | | | | | | | if a process's uid or gid has changed, but the /proc/<PID> directory itself was also set to mode 0. Assuming this doesn't open any security holes, open access to the /proc/<PID> directory for users other than root to read or search the directory. Reviewed by: des (back in February) MFC after: 3 weeks
* Implement internal (i.e. inside kernel) packet tagging using mbuf_tags(9).oleg2006-05-244-10/+196
| | | | | | | | | | | Since tags are kept while packet resides in kernelspace, it's possible to use other kernel facilities (like netgraph nodes) for altering those tags. Submitted by: Andrey Elsukov <bu7cher at yandex dot ru> Submitted by: Vadim Goncharov <vadimnuclight at tpu dot ru> Approved by: glebius (mentor) Idea from: OpenBSD PF MFC after: 1 month
* Rename device name in the last commit. According to PR, the ID isglebius2006-05-242-5/+5
| | | | | | | more likely to belong to chips of 8168 family. PR: kern/96734 Submitted by: Sven Petai <hadara bsd.ee>
* Convert to nmount() and remove hardcoded checks for ufs, msdosfs, ntfs,rodrigc2006-05-241-25/+19
| | | | | | and cd9660. PR: bin/97642
* Quote the parameter to sysctl(1), allowing to use whitespaces inglebius2006-05-241-1/+1
| | | | | | | sysctl values. PR: conf/96509 Submitted by: Gregory Bond <gnb itga.com.au>
* Remove the trailing half of a sentence which was clearly supercededceri2006-05-241-2/+0
| | | | by the preceding one some time during editing.
* Clean up the grammar in here some.ceri2006-05-241-31/+32
|
* GC long unused hostnamelen and domainnamelen.ru2006-05-241-2/+0
| | | | Submitted by: Alex Lyashkov <shadow@psoft.net>
* If the user asks for "kernel sources" to be installed, extract thecperciva2006-05-241-1/+1
| | | | | | | | | SRC_BASE package (src/[A-Z]*) as well as SRC_SYS (src/sys/*). This allows users who only install the kernel source code to use the modern "make buildkernel" approach. Discussed with: re (scottl, kensmith) MFC after: 3 days
* Attempt to follow the procedure described in section 4.10 of theiedowse2006-05-242-94/+224
| | | | | | | | | | | | | | | | | | | | EHCI spec for linking in new qTDs into an asynchronous QH. This requires that there is a qTD marked as not active and not halted at the start of the QH's list, and the hardware will know to re-fetch the qTD on each pass rather than just looking at the overlay qTD: "The host controller must be able to advance the queue from the Fetch QH state in order to avoid all hardware/software race conditions. This simple mechanism allows software to simply link qTDs to the queue head and activate them, then the host controller will always find them if/when they are reachable." This is achieved by keeping an "inactivesqtd" entry on the QH list, and re-using it each time as the start of the next transfer, and allocating a new qTD to become the next inactivesqtd. Then a new transfer can be activated by just setting its "active" flag, which avoids all the previous messing with overlay qTD state in ehci_set_qh_qtd().
* Take errmsg out of ffs_opts. It is already part of global_optsrodrigc2006-05-241-1/+1
| | | | in vfs_mount.c.
* Increase the nfs access cache timeout from 2 to 60. The latter is akris2006-05-241-1/+1
| | | | | | | | | | | more appropriate value and is also the default set by the kernel. I could not find a justification of why rc.conf began overriding it back in 1998. This dramatically cuts NFS traffic on e.g. a busy system with NFS root. Reviewed by: mohans MFC After: 2 weeks
* Whitespace nitsimp2006-05-231-3/+3
|
* The (British) Crown Dependencies now have their own codes.wollman2006-05-231-1/+8
|
* Remove definitions of uart_[gs]etdreg. They are not used anymore andmarcel2006-05-231-6/+0
| | | | were in fact wrong.
* Add a stub man page for device_get_sysctl{_ctx,tree}. Needs someimp2006-05-232-0/+61
| | | | work, but is better than nothing. Any help appreciated.
* NFS over TCP retransmit behavior should default to a 60 second time out,cel2006-05-233-5/+17
| | | | | | | | | | | | mimicing the NFS reference implementation. NFS over TCP does not need fast retransmit timeouts, since network loss and congestion are managed by the transport (TCP), unlike with NFS over UDP. A long timeout prevents the unnecessary retransmission of non- idempotent NFS requests. Reviewed by: mohans, silby, rees? Sponsored by: Network Appliance, Incorporated
* Refactor the NFS over UDP retransmit timeout estimation logic to allowcel2006-05-233-62/+158
| | | | | | | | | | | | | the estimator to be more easily tuned and maintained. There should be no functional change except there is now a lower limit on the retransmit timeout to prevent the client from retransmitting faster than the server's disks can fill requests, and an upper limit to prevent the estimator from taking to long to retransmit during a server outage. Reviewed by: mohan, kris, silby Sponsored by: Network Appliance, Incorporated
* Convert mountd to nmount(). Remove some hardcoded dependenciesrodrigc2006-05-232-69/+142
| | | | on ufs, cd9660, msdosfs, and ntfs, but not all dependencies.
* Remove 'n' from the getopt string. There's no -n option that isimp2006-05-231-2/+2
| | | | | | parsed, so it winds up at usage anyway. Add 'b' to the usage summary. Noticed by Ben Mesander.
* Vnode locks are recursive and the NFS client support shared vnode locks.mohans2006-05-231-0/+5
| | | | Found by: Kris Kennaway.
* Use pmap_devmap_bootstrap(), instead of mapping the SACOM1 registerscognet2006-05-234-6/+42
| | | | | | | with pmap_map_entry. More use of macros instead of hardcoding the addr. Submitted by: kevlo
* Forgot to remove the line.pjd2006-05-231-1/+0
|
* Document missing CRYPTO_F_ flags.pjd2006-05-231-1/+15
|
* The lcr variable in ns8250_probe is now unused. Remove it.benno2006-05-231-1/+1
| | | | Missed by: benno
* GC old a.out and K&R support.imp2006-05-231-9/+0
|
* When usb_event_thread() first starts, wait significantly longeriedowse2006-05-231-5/+14
| | | | | | | | | | | | | | | | before starting exploring (4 seconds), and extend the wait period if new USB buses are attached while waiting. This works around a problem seen when there is more than one EHCI controller in the system and you kldload usb.ko after the system has booted. The problem is that usb.ko contains 3 separate PCI drivers which get initialised one by one (uhci, ohci, ehci), and when each driver is initialised, all PCI buses are re-probed after just the addition of that driver. This means that there can be a significant delay between the attaching of a companion controller and the subsequent EHCI attach, so it is possible for the companion controller's USB 1.x bus to be scanned before the EHCI driver gets a chance to check if there is really a USB 2.x device connected.
* Allow uart(4)'s ns8250 driver to work with devices whose regshift is > 0.benno2006-05-232-25/+18
| | | | | | | | | | | | | - Rename REG_DL to REG_DLL and REG_DLH. - Always treat DLL and DLH as two separate 8-bit registers instead of one 16-bit register. Additionally, remove the probe for the high 4 bits of IER being 0 and don't assume we can always read/write 0 to/from those bits. These changes allow uart(4) to drive the UARTs on the Intel XScale PXA255. Reviewed by: marcel
* Avoid spurious release of an rtentry.tanimura2006-05-231-3/+3
|
* Use macros instead of hardcoding the address for SACOM1. Also don'tcognet2006-05-223-4/+7
| | | | | | pretend we're working with SACOM3, as we're really mapping SACOM1. Submitted by: kevlo
* New release notes: ipfwpcap(8), jemalloc.bmah2006-05-222-2/+32
| | | | Modified release note: Add a missing word in mdmfs(8) -P note.
* GC these crt{begin,end}.c, which are unused since the last FreeBSD platformmarius2006-05-222-114/+0
| | | | switched to those created from GCC's crtstuff.c 4 years ago.
OpenPOWER on IntegriCloud