summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
...
* Improve inittodr(). Assume the real-time clock is reliable and onlymarcel2005-11-201-52/+40
| | | | | | | | | use the base time in case the real-time clock is bogus or behind the base time. Most importantly, don't sanity-check the base time up front because it may be zero. This is not a preposterous condition. It just means that none of the file systems have their mount time updated. MFC after: 1 week
* Correct the API for Windows interupt handling a little. The prototypewpaul2005-11-202-11/+13
| | | | | | | | | | | | | | | | | | | | | | | for a Windows ISR is 'BOOLEAN isrfunc(KINTERRUPT *, void *)' meaning the ISR get a pointer to the interrupt object and a context pointer, and returns TRUE if the ISR determines the interrupt was really generated by the associated device, or FALSE if not. I had mistakenly used 'void isrfunc(void *)' instead. It happens the only thing this affects is the internal ndis_intr() ISR in subr_ndis.c, but it should be fixed just in case we ever need to register a real Windows ISR vi IoConnectInterrupt(). For NDIS miniports that provide a MiniportISR() method, the 'is_our_intr' value returned by the method serves as the return value from ndis_isr(), and 'call_isr' is used to decide whether or not to schedule the interrupt handler via DPC. For drivers that only supply MiniportEnableInterrupt() and MiniportDisableInterrupt() methods, call_isr is always TRUE and is_our_intr is always FALSE. In the end, there should be no functional changes, except that now ntoskrnl_intr() can terminate early once it finds the ISR that wants to service the interrupt.
* Add more options to ffs_opts, so that vfs_filteropts() will notrodrigc2005-11-191-2/+3
| | | | | complain when we pass these options to a UFS filesystem as strings via nmount(): noexec, nosuid, nosymfollow, sync, suiddir
* Return 0 if we are a network card and do match. Previously, we'd boguslyimp2005-11-191-0/+1
| | | | | | fail and the card wouldn't be detected. Submitted by: Bryan Blackburn
* Fix bug introduced in revision 1.186:marcel2005-11-191-3/+8
| | | | | | | | | | | | | | | | | | | | When all file systems have a time stamp of zero, which is the case for example when the root file system is on a read-only medium, we ended up not calling inittodr() at all. A potential uncleanliness existed as well. If multiple file systems had a non-zero time stamp, we would call inittodr() multiple times. While this should not be harmful, it's definitely not ideal. Fix both issues by iterating over the mounted file systems to find the largest time stamp and call inittodr() exactly once with that time stamp. This could of course be a zero time stamp if none of the mounted file systems have a non-zero time stamp. In that case the annoying errors mentioned in the commit log for revision 1.186 still haven't been avoided. The bottom line is that inittodr() should not complain when it gets a time base of zero. At the time of this commit only alpha seems to have that problem. Reported by: Dario Freni (saturnero at freesbie dot org) MFC after: 1 week
* Parse more mount options in vfs_donmount(), before vfs_domount()rodrigc2005-11-191-0/+42
| | | | | | | | | | | | is called. It looks like there are lots of different mount flags checked in vfs_domount(), so we need to do the parsing for these particular mount flags earlier on. The new flags parsed are: async, force, multilabel, noasync, noatime, noclusterr, noclusterw, noexec, nosuid, nosymfollow, snapshot, suiddir, sync, union. Existing code which uses mount() to mount UFS filesystems is not affected, but new code which uses nmount() to mount UFS filesystems should behave better.
* Finally bring in what was produced during Google SoC 2005:le2005-11-197-5/+515
| | | | | | | | | Add functions to rename objects and to move a subdisk from one drive to another. Obtained from: Chris Jones <chris.jones@ualberta.ca> Sponsored by: Google Summer of Code 2005 MFC in: 1 week
* Remove 'ipprintfs' which were protected under DIAGNOSTIC. It doesn'tandre2005-11-192-36/+0
| | | | | | | | | | have any know to enable it from userland and could only be enabled by either setting it to 1 at compile time or through the kernel debugger. In the future it may be brought back as KTR tracing points. Discussed with: rwatson Sponsored by: TCP/IP Optimization Fundraise 2005
* Load firmware images directly from the filesystem (looks into /etc/firmwaredamien2005-11-194-154/+166
| | | | | | | | directory by default) without requiring the user to load them by hand using e.g iwicontrol. Get rid of the old ioctl crud. Updated iwi-firmware port coming soon. Obtained from: OpenBSD
* Properly parse the nowin95 mount option.rodrigc2005-11-191-5/+4
| | | | Tested by: Rainer Hurling <rhurlin at gwdg dot de>
* Minor tweaks.damien2005-11-191-10/+13
|
* Move MAX_IPOPTLEN and struct ipoption back into ip_var.h asandre2005-11-192-13/+13
| | | | | | | userland programs depend on it. Pointed out by: le Sponsored by: TCP/IP Optimization Fundraise 2005
* Add "shortnames" and "longnames" mount options which arerodrigc2005-11-181-1/+5
| | | | | | | | | | synonyms for "shortname" and "longname" mount options. The old (before nmount()) mount_msdosfs program accepted "shortnames" and "longnames", but the kernel nmount() checked for "shortname" and "longname". So, make the kernel accept "shortnames", "longnames", "shortname", "longname" for forwards and backwarsd compatibility. Discovered by: Rainer Hurling <rhurlin at gwdg dot de>
* Second part of the AMRR commit.damien2005-11-182-13/+112
| | | | | Enable automatic rate adaptation in BSS operating mode. Works great here. Will need a lot of testing though.
* Consolidate all IP Options handling functions into ip_options.[ch] andandre2005-11-1815-681/+795
| | | | | | | | | | | | | | | | | | | | include ip_options.h into all files making use of IP Options functions. From ip_input.c rev 1.306: ip_dooptions(struct mbuf *m, int pass) save_rte(m, option, dst) ip_srcroute(m0) ip_stripoptions(m, mopt) From ip_output.c rev 1.249: ip_insertoptions(m, opt, phlen) ip_optcopy(ip, jp) ip_pcbopts(struct inpcb *inp, int optname, struct mbuf *m) No functional changes in this commit. Discussed with: rwatson Sponsored by: TCP/IP Optimization Fundraise 2005
* Add sanity checking for QUEUE(3) lists under INVARIANTS. Races may leademaste2005-11-181-2/+35
| | | | | | | | | | | | to list corruption, which can be difficult to unravel in a post-mortem analysis. These checks verify that prev and next pointers are consistent when inserting or removing elements, thus catching any corruption earlier. Also use TRASHIT to break LIST and SLIST link pointers on element removal, from mlaier via -hackers. Reviewed by: mlaier Approved by: rwatson (mentor)
* - Always print the trap number so that we have something to start with forjhb2005-11-182-9/+19
| | | | | | | | mystery traps. If we don't have a message for a given trap, just use UNKNOWN for the message. - Add trap messages for T_XMMFLT and T_RESERVED. MFC after: 1 week
* Add CLOCK_UPTIME to clock_gettime(2) reporting the currentandre2005-11-182-0/+3
| | | | | | uptime measured in SI seconds. Sponsored by: TCP/IP Optimization Fundraise 2005
* Add support for a new/unreleased Pentium-M.ps2005-11-181-1/+1
| | | | Reviewed by: jkoshy
* Purge layer specific mbuf flags on layer crossings to avoid confusingandre2005-11-183-1/+20
| | | | | | upper or lower layers. Sponsored by: TCP/IP Optimization Fundraise 2005
* Rework icmp_error() to deal with truncated IP packets fromandre2005-11-181-48/+54
| | | | | | ip_forward() when doing extended quoting in error messages. Sponsored by: TCP/IP Optimization Fundraise 2005
* In ip_forward() copy as much into the temporary error mbuf as weandre2005-11-181-3/+2
| | | | | | | | have free space in it. Allocate correct mbuf from the beginning. This allows icmp_error() to quote the entire TCP header in error messages. Sponsored by: TCP/IP Optimization Fundraise 2005
* Add KASSERTs to M_ALIGN() and MH_ALIGN() to prevent usage on wrongandre2005-11-181-0/+8
| | | | | | mbuf types. Sponsored by: TCP/IP Optimization Fundraise 2005
* -mdoc sweep.ru2005-11-181-3/+2
|
* - Add parsing for the following existing UFS/FFS mount options in the nmount()rodrigc2005-11-181-1/+33
| | | | | | | | | | callpath via vfs_getopt(), and set the appropriate MNT_* flag: -> acls, async, force, multilabel, noasync, noatime, -> noclusterr, noclusterw, snapshot, update - Allow errmsg as a valid mount option via vfs_getopt(), so we can later add a hook to propagate mount errors back to userspace via vfs_mount_error().
* Fix a bug that caused some /dev entries to continue to exist afterjdp2005-11-185-2/+18
| | | | | | | | | | | | | | | | | | | | | | | the underlying drive had been hot-unplugged from the system. Here is a specific example. Filesystem code had opened /dev/da1s1e. Subsequently, the drive was hot-unplugged. This (correctly) caused all of the associated /dev/da1* entries to be deleted. When the filesystem later realized that the drive was gone it closed the device, reducing the write-access counts to 0 on the geom providers for da1s1e, da1s1, and da1. This caused geom to re-taste the providers, resulting in the devices being created again. When the drive was hot-plugged back in, it resulted in duplicate /dev entries for da1s1e, da1s1, and da1. This fix adds a new disk_gone() function which is called by CAM when a drive goes away. It orphans all of the providers associated with the drive, setting an error condition of ENXIO in each one. In addition, we prevent a re-taste on last close for writing if an error condition has been set in the provider. Sponsored by: Isilon Systems Reviewed by: phk MFC after: 1 week
* In vfs_nmount(), check to see if "update" mount option was passedrodrigc2005-11-181-0/+9
| | | | | | | in, and if so, set MNT_UPDATE filesystem flag. vfs_nmount() calls vfs_domount(), and there is special logic inside vfs_domount() if MNT_UPDATE is set. This is very important when we want to do an update mount of the root filesystem, using nmount().
* MFOpenBSD 1.62:glebius2005-11-171-2/+4
| | | | | | | Prevent backup CARP hosts from replying to arp requests, fixes strangeness with some layer-3 switches. From Bill Marquette. Tested by: Kazuaki Oda <kaakun highway.ne.jp>
* - Backout last change, since it is memory overkill for a non busy host orglebius2005-11-173-13/+44
| | | | | | | | | | | | | | | for a notebook with em(4) adapter. - Introduce tunables em.hw.txd and em.hw.rxd, which allow administrator to configure number of transmit and receive descriptors. - Check em.hw.txd and em.hw.rxd against hardware limits [*] and require them to be multiple of 128. [*] According to comments in if_em.h the 82540EM/82541ER chips can handle more than 256 descriptors. Since we don't have this hardware to test, we decided to mimic NetBSD wm(4) driver, that limits these chips to 256 descriptors. In collaboration with: yongari
* Prefer NULL to 0.yongari2005-11-171-25/+29
| | | | | | | | | Add missing lock/unlock in sysctl handler. Protect accessing NULL pointer when resource allocation was failed. style(9) Reviewed by: scottl MFC after: 1 week
* Remove vestiges of oldcard and owi.ru2005-11-172-19/+0
|
* Fix spelling mistake.obrien2005-11-172-2/+2
| | | | Submitted by: kris
* Make the elf wrapper work with recent kernel.debug changes.cognet2005-11-171-3/+5
|
* OBEimp2005-11-161-9/+0
|
* Revert a part of the previous commits to these files that made the NMIjhb2005-11-162-10/+8
| | | | | | | | | IPI_STOP handling code use atomic_readandclear() to execute the restart function on the first CPU to resume and restore the behavior of always executing the restart function on the BSP since this is in fact what the non-NMI IPI_STOP handler does. I did add back in a statement to clear the restart function pointer after it is executed to match the behavior of the non-NMI IPI_STOP handler.
* this is no longer needed.imp2005-11-165-3721/+0
|
* Revert previous commit to these files. There isn't a race necessitatingjhb2005-11-162-6/+4
| | | | | an xchg instruction as we only try to execute the startup function if the CPU ID is 0 (i.e. the BSP). I missed this earlier.
* Fix a typo in the check for an invalid APIC. If we are told about anjhb2005-11-162-2/+2
| | | | | | | | | I/O APIC that doesn't exist, then a read of the version register is going to return -1 which is 0xffffffff not 0xffffff. Tested on: i386 Tested by: Nikos Ntarmos ntarmos at ceid dot upatras dot gr MFC after: 1 week
* Correct description of RLIMIT_CPU.jhb2005-11-161-1/+1
| | | | Reported by: bde
* fixed a kernel crash due to an improper removal of callout-timersuz2005-11-161-0/+1
| | | | | | | | (ToDo: similar fix is necessary for other NDP-related callout-timers in netinet6/nd6*.c) PR: kern/88725 MFC after: 1 month
* - Add errmsg to the list of smbfs mount options.rodrigc2005-11-161-7/+23
| | | | | | - Use vfs_mount_error() to propagate smbfs mount errors back to userspace. Reviewed by: bp (smbfs maintainer)
* Catch up with loader_color -> loader_logo and document beastie_disable.ru2005-11-152-5/+12
|
* Provide a link to the documentation of the I/O APIC at Intel.andre2005-11-151-0/+4
|
* Add some initial bits (currently unused) for upcoming AMRR support.damien2005-11-151-0/+10
| | | | | | | AMRR = Adaptive Multi Rate Retry algorithm More information: http://www-sop.inria.fr/rapports/sophia/RR-5208.html More to come.
* Add some initial bits (currently unused) for upcoming AMRR support.damien2005-11-151-0/+77
| | | | | AMRR = Adaptive Multi Rate Retry algorithm More information: http://www-sop.inria.fr/rapports/sophia/RR-5208.html
* Optimize and clean TX time computation.damien2005-11-152-44/+14
| | | | | | Avoid a test and a modulus operation. MFC after: 2 weeks
* Recognize Broadcom BCM5752 chip, that can be found in HP DC7600.glebius2005-11-152-2/+7
| | | | | PR: kern/88940 Submitted by: Alexander Hausner
* Some whitespace and style cleanup.glebius2005-11-152-89/+88
|
* Update ieee80211_mhz2ieee to understand public safety bands and spectrumsam2005-11-152-9/+24
| | | | | | | that can potentially be mapped to negative ieee #'s. NB: before operation on the latter can be supported we need to cleanup various code that assumes ieee channel #'s are >= 0
* nuke special handling to extend cts when bursting; it was race pronesam2005-11-153-65/+2
| | | | MFC after: 7 days
OpenPOWER on IntegriCloud