summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Changes to allow top to decide whether or not to show multiple threads perjulian2003-07-175-6/+27
| | | | | | | process. Option -H enables it and it is toggled at the interactive screen by 'H'. Submitted by: Jung-uk Kim <jkim@niksun.com>
* To avoid a kernel panic provoked by a NULL pointer dereference,robert2003-07-172-1/+8
| | | | | | | | | | | | | | | | do not clear the `sb_sel' member of the sockbuf structure while invalidating the receive sockbuf in sorflush(), called from soshutdown(). The panic was reproduceable from user land by attaching a knote with EVFILT_READ filters to a socket, disabling further reads from it using shutdown(2), and then closing it. knote_remove() was called to remove all knotes from the socket file descriptor by detaching each using its associated filterops' detach call- back function, sordetach() in this case, which tried to remove itself from the invalidated sockbuf's klist (sb_sel.si_note). PR: kern/54331
* Avoid exposing declarations for kernel variables to userland.jake2003-07-171-0/+4
| | | | PR: 54528
* o Eliminate upcall for PTHREAD_SYSTEM_SCOPE thread, now itdavidxu2003-07-1732-790/+1204
| | | | | | | | | | | | | is system bound thread and when it is blocked, no upcall is generated. o Add ability to libkse to allow it run in pure 1:1 threading mode, defining SYSTEM_SCOPE_ONLY in Makefile can turn on this option. o Eliminate code for installing dummy signal handler for sigwait call. o Add hash table to find thread. Reviewed by: deischen
* Fix sigwait to conform to POSIX.davidxu2003-07-171-67/+109
| | | | | | | | | | | When a signal is being delivered to process, first find a sigwait thread to deliver, POSIX's argument is speed of delivering signal to sigwait thread is faster than other ways. A signal in its wait set will cause sigwait to return the signal number, a signal not in its wait set but in not blocked by the thread also causes sigwait to return, but sigwait returns EINTR, sigwait is oneshot operation, only one signal can be delivered to its wait set, when a signal is delivered to the sigwait thread, the thread's sigwait state is canceled.
* o Refine kse_thr_interrupt to allow it to handle different commands.davidxu2003-07-1710-134/+138
| | | | | | | o Remove TDF_NOSIGPOST. o Add a member td_waitset to proc structure, it will be used for sigwait. Tested by: deischen
* Correct six return statements which returned zero instead ofrobert2003-07-171-9/+10
| | | | | | | | | | an appropriate error number after a failure condition. In particular, three of the changed statements return ESRCH for a failed pfind(), and in also three places a non-zero return from p_cansee() will be passed back, Also noticed by: rwatson
* Make sure that SWP_NPAGES always has the same value in all sourcephk2003-07-172-7/+5
| | | | | | | | | | | files, so that SWAP_META_PAGES does not vary either. swap_pager.c ended up with a value of 16, everybody else 8. Go with the 16 for now. This should only have any effect in the "kill processes because we are out of swap" scenario, where it will make some sort of estimate of something more precise.
* Style(9) cleanup. There was no consistent style in this driver, andmarkm2003-07-177-912/+830
| | | | | | | The next round of commits will be to fix up locking in it. This lot is to at least give a consistent base to work off. OK'ed by: imp, mdodd
* Fix a bogon in the previous commit. When suppressing multiple isabjhb2003-07-171-1/+1
| | | | | | devices, we have to allow for the case when the isab0 device is ourselves. Tested by: markm
* Correct comments to indicate that the EM_RADV and EM_TADV parametersjdp2003-07-171-2/+2
| | | | are not applicable to the 82544.
* New release notes: ipfw(8) -n flag, comma-separeted address lists.hrs2003-07-172-6/+34
| | | | MFC: ipfw(4) C++-style comment, rules in set 31.
* This file became OBE when we went to GCC 3.obrien2003-07-171-257/+0
|
* NO_TCSH would be set in /etc/make.conf, not here. Also obey NO_IPFILTER.obrien2003-07-171-5/+6
|
* consistify the style someobrien2003-07-171-41/+42
|
* Now that the dust has settled, make dflt_lock() always panic.scottl2003-07-171-4/+0
|
* Add quirk entry for IntelligentStick disc-on-key USB devices.thomas2003-07-171-0/+8
| | | | | | | Reported by Samuel Tardieu <sam@rfc1149.net>. Reviewed by: roberto MFC after: 1 week
* The card resets the S/Uni chip when it is resetted. Thereforharti2003-07-171-0/+5
| | | | | we need to reinitialize the PHY after the call to reset when stopping the interface.
* Drop Giant around syncache timer processing.hsu2003-07-171-1/+1
|
* Fix umtx locking, for libthr, in the kernel.mtm2003-07-172-24/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. There was a race condition between a thread unlocking a umtx and the thread contesting it. If the unlocking thread won the race it may try to wakeup a thread that was not yet in msleep(). The contesting thread would then go to sleep to await a wakeup that would never come. It's not possible to close the race by using a lock because calls to casuptr() may have to fault a page in from swap. Instead, the race was closed by introducing a flag that the unlocking thread will set when waking up a thread. The contesting thread will check for this flag before going to sleep. For now the flag is kept in td_flags, but it may be better to use some other member or create a new one because of the possible performance/contention issues of having to own sched_lock. Thanks to jhb for pointing me in the right direction on this one. 2. Once a umtx was contested all future locks and unlocks were happening in the kernel, regardless of whether it was contested or not. To prevent this from happening, when a thread locks a umtx it checks the queue for that umtx and unsets the contested bit if there are no other threads waiting on it. Again, this is slightly more complicated than it needs to be because we can't hold a lock across casuptr(). So, the thread has to check the queue again after unseting the bit, and reset the contested bit if it finds that another thread has put itself on the queue in the mean time. 3. Remove the if... block for unlocking an uncontested umtx, and replace it with a KASSERT. The _only_ time a thread should be unlocking a umtx in the kernel is if it is contested.
* When reporting errors binding IPv6 TCP sockets, don't call them UDPrwatson2003-07-171-3/+3
| | | | | | | | sockets in the printf. Fix two minor co-located whitespace glitches. Product of: France
* Remove the commented out 'rmail' before someone gets a really bad idea.obrien2003-07-171-3/+0
|
* Fix a grammar bogon and a typobrueffer2003-07-171-1/+1
| | | | | Submitted by: Warren Block <wblock@wonkity.com> MFC after: 3 days
* *major* style problems.obrien2003-07-171-12/+15
|
* We don't need so many -I's.obrien2003-07-171-2/+0
|
* Fix the ski loader, broken by the gcc upgrade. Update the linkermarcel2003-07-178-262/+230
| | | | | | script to match the one for the EFI loader and rewrite __start() in assembly to have gp defined without getting in the way of the compiler.
* Have the linker script look more like the default linker scriptmarcel2003-07-172-92/+78
| | | | | on ia64. This fixes the breakage caused by the gcc upgrade that resulted in a broken executable.
* Very big makeover in the way telnet, telnetd and libtelnet are built.markm2003-07-16106-43872/+64
| | | | | | | | | | | | | | | | | | | | | | | Previously, there were two copies of telnet; a non-crypto version that lived in the usual places, and a crypto version that lived in crypto/telnet/. The latter was built in a broken manner somewhat akin to other "contribified" sources. This meant that there were 4 telnets competing with each other at build time - KerberosIV, Kerberos5, plain-old-secure and base. KerberosIV is no longer in the running, but the other three took it in turns to jump all over each other during a "make buildworld". As the crypto issue has been clarified, and crypto _calls_ are not a problem, crypto/telnet has been repo-copied to contrib/telnet, and with this commit, all telnets are now "contribified". The contrib path was chosen to not destroy history in the repository, and differs from other contrib/ entries in that it may be worked on as "normal" BSD code. There is no dangerous crypto in these sources, only a very weak system less strong than enigma(1). Kerberos5 telnet and Secure telnet are now selected by using the usual macros in /etc/make.conf, and the build process is unsurprising and less treacherous.
* Change the style of the english used to print accounting enabledbmilekic2003-07-161-2/+2
| | | | | | | and disabled. This means no period at the end and changing "Process accounting <foo>" to "Accounting <foo>". Pointed out by: bde
* Some grammatical and markup fixes.hrs2003-07-162-4/+6
|
* New release notes: ipfw(8), and atkbd(4) bug fix.hrs2003-07-162-0/+24
|
* Fix a typo.truckman2003-07-161-1/+1
|
* Document mutex pool API enhancements that allow creation and use oftruckman2003-07-162-19/+68
| | | | multiple mutex pools.
* seems like i386 && DIAGNOSTIC needs sys/proc.hjmg2003-07-161-0/+1
| | | | Noticed by: tinderbox
* Nuke the declaration of a function which was not implemented.truckman2003-07-161-1/+0
|
* Fix a typo.rushani2003-07-161-1/+1
| | | | Submitted by: Pawel Worach <pawel.worach@telia.com>
* Document the latest controllers from 3ware as being supported.ps2003-07-161-2/+14
|
* Log process accounting activation/deactivation.bmilekic2003-07-161-0/+2
| | | | | | | Useful for some auditing purposes. Submitted by: Christian S.J. Peron <maneo@bsdpro.com> PR: kern/54529
* add missing machine/bus.h that is necessary to build now that usb is bus_dmajmg2003-07-161-0/+1
| | | | aware.
* add missing machine/bus.h headers that are now necessary because of thejmg2003-07-166-0/+6
| | | | bus_dma addition.
* change CLASS depending upon __ELF_WORD_SIZE. This is necessary ifjmg2003-07-161-1/+5
| | | | someone wants to try to run 32bit binaries on sparc64.
* Rearrange the SYSINIT order to call lockmgr_init() earlier so thattruckman2003-07-163-29/+6
| | | | | | the runtime lockmgr initialization code in lockinit() can be eliminated. Reviewed by: jhb
* Add support for the BCM5705 and its ilk. Changes:wpaul2003-07-164-111/+325
| | | | | | | | | | | | | | | | | | | - 5705 doesn't support jumbo frames - Statistics must be read from registers - RX return ring must be capped at 512 entries - Omit initialization of certain device blocks - Acknowledge link change interrupts by setting the 'link changed' bit in the status register (used to have no effect) - Remember to toggle the MI completion bit too - Set the mbuf low watermark differently (on-chip memory buffers, not BSD mbufs) - Don't enable Ethernet@WireSpeed feature for certain 5705 chip revs - Add additional PCI IDs for 5705 and 5782 parts - Add a forgotten 5704 PCI ID Most changes ripped kicking and screaming from the Broadcom linux driver. Thanks to Paul Saab for sanity testing. (My lack of sanity has been confirmed.)
* add support for interrupt counting on sparc64. This copies part of thejmg2003-07-166-4/+125
| | | | | | | | | code from i386. The code has a slight bogon that interrupts are counted twice. Once on the ithread dispatch and once on the dispatch for the vector vmstat -i and systat -vm now contains interrupt counts. Reviewed by: jake
* make allocation of the necessary data structures most efficent by usingjmg2003-07-152-5/+5
| | | | | | a full page instead of only part of a page. Reviewed by: joe
* fix support for umass and related devices on ohci. This is a partialjmg2003-07-153-79/+151
| | | | | | | | | | | sync of the NetBSD code. fix isochornous support for ohci. This gets webcams like my OV511 working on sparc64. PR: kern/52589 Submitted by: Bruce R. Montague (isochonous support) Reviewed by: joe among others
* Userland side of:luigi2003-07-152-14/+22
| | | | | | | | | | | | | | Allow set 31 to be used for rules other than 65535. Set 31 is still special because rules belonging to it are not deleted by the "ipfw flush" command, but must be deleted explicitly with "ipfw delete set 31" or by individual rule numbers. This implement a flexible form of "persistent rules" which you might want to have available even after an "ipfw flush". Note that this change does not violate POLA, because you could not use set 31 in a ruleset before this change. Suggested by: Paul Richards
* Allow set 31 to be used for rules other than 65535.luigi2003-07-152-23/+28
| | | | | | | | | | | | | | | Set 31 is still special because rules belonging to it are not deleted by the "ipfw flush" command, but must be deleted explicitly with "ipfw delete set 31" or by individual rule numbers. This implement a flexible form of "persistent rules" which you might want to have available even after an "ipfw flush". Note that this change does not violate POLA, because you could not use set 31 in a ruleset before this change. sbin/ipfw changes to allow manipulation of set 31 will follow shortly. Suggested by: Paul Richards
* make usb bus_dma aware.jmg2003-07-1510-102/+362
| | | | Reviewed by: joe among others
* sync w/ NetBSDjmg2003-07-152-4/+4
| | | | | | part of: revision 1.101 date: 2002/06/01 23:51:04; author: lukem; state: Exp; lines: +5 -7
OpenPOWER on IntegriCloud