summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add mutex for routing entries.hsu2003-07-191-1/+8
| | | | Reviewed by: bmilekic, silby
* Adjust for new telnet situation (single telnet source tree).markm2003-07-191-3/+2
|
* Revert to using yp_order() to probe for master.paswd.by* maps andwpaul2003-07-181-7/+14
| | | | | | | | | | | | | | | don't probe the server at all for passwd.by* maps. This fixes interoperability with the Services For UNIX NIS server (which is really a front end to Captive^WActiveDirectory). This server incorrectly returns success for all YPPROC_MASTER requests, even for maps that don't exist, which makes it impossible to (ab)use it to probe for the existence of the master.passwd.by* maps. This is a little kludgey, but basically restores the original behavior of getpwent.c as it is in -stable, and works around both the lack of YPPROC_ORDER on NIS+ servers as well as the broken YPPROC_MASTER on Services For UNIX servers.
* Fix a busdma bogon:wpaul2003-07-181-3/+3
| | | | | | Some of the calls to bus_dmamap_sync() were syncing the DMA descriptor ring maps using the mbuf tag, when they should have been using the descriptor ring tag instead.
* Fix a printf format warning I introduced.phk2003-07-181-21/+19
| | | | | | Use the macro max number of swap devices rather than cache the constant in a variable. Avoid a (now) pointless variable.
* Report the I/O base address in hex to be consistent with itsdds2003-07-181-1/+1
| | | | | | | specification format. Approved by: schweikh (mentor) MFC after: 2 weeks
* Remove a lock held across casuptr() that snuck in last commit.mtm2003-07-181-2/+5
|
* New release notes: top(1) -H, mount(8)/umount(8) filesystem ID support.hrs2003-07-182-2/+20
|
* Move the decision on whether to unset the contestedmtm2003-07-181-48/+40
| | | | | | bit or not from lock to unlock time. Suggested by: jhb
* When mount(8) is invoked with the `-v' flag, display the filesystemiedowse2003-07-183-17/+54
| | | | | | | | | | | | ID for each file system in addition to the normal information. In umount(8), accept filesystem IDs as well as the usual device and path names. This makes it possible to unambiguously specify which file system is to be unmounted even when two or more file systems share the same device and mountpoint names (e.g. NFS mounts from the same export into different chroots). Suggested by: Dan Nelson <dnelson@allantgroup.com>
* Fix a number of occurences of calling uma_zalloc() with neitherharti2003-07-182-13/+13
| | | | M_WAITOK nor M_NOWAIT.
* Reference PR for IntelligentStick quirk entry.thomas2003-07-181-1/+1
| | | | PR: kern/53005
* Prototype defttymode() instead of just declaring it.yar2003-07-181-1/+1
|
* Add a comment above rip_ctloutput() documenting that the privilegerwatson2003-07-181-0/+10
| | | | | | | | | | | check for raw IP system management operations is often (although not always) implicit due to the namespacing of raw IP sockets. I.e., you have to have privilege to get a raw IP socket, so much of the management code sitting on raw IP sockets assumes that any requests on the socket should be granted privilege. Obtained from: TrustedBSD Project Product of: France
* When INVARIANTS is defined make sure that uma_zalloc_arg (and henceharti2003-07-181-0/+20
| | | | | | | uma_zalloc) is called with exactly one of either M_WAITOK or M_NOWAIT and that it is called with neither M_TRYWAIT or M_DONTWAIT. Print a warning if anything is wrong. Default to M_WAITOK of no flag is given. This is the same test as in malloc(9).
* Whitespace after keywords per style(9).wollman2003-07-181-2/+2
|
* When reporting an error internalizing an ACL string, print out therwatson2003-07-181-2/+2
| | | | | | | | ACL that generated the error, rather than the function, which is more user-friendly. Obtained from: TrustedBSD Project Product of: France
* Correct a couple of slips: add a missing article at one pointyar2003-07-182-4/+4
| | | | and the plaintext word "option" after "</option>" at another.
* Clean up include files.simokawa2003-07-186-23/+6
|
* New release note: arp(8) -i.yar2003-07-182-0/+12
|
* Remove extern declaration of ps_showallprocs. The definition is already gone.tjr2003-07-181-1/+0
| | | | | PR: 54604 Submitted by: Pawel Jakub Dawidek
* Implement a new option: -i, which will allow to limityar2003-07-182-4/+33
| | | | | | | | | | | the scope of operation to the ARP entries on a particular interface. It should be useful on machines with numerous network interfaces, e.g., on inter-VLAN routers. PR: bin/54151 Submitted by: Dmitry Morozovsky <marck at rinet.ru> Discussed on: -net MFC after: 2 weeks
* Big fixup of the makefiles. Sort out the dependancies so that "make"markm2003-07-1826-675/+835
| | | | | without "make depend" works, "make -j N" works, and lists of source files are made vertical to reduce future diffs.
* WLAN related fixes:hmp2003-07-185-6/+14
| | | | | | | | | | - Add some wlan(4) related cross-references. - Add some "device" lines to SYNOPSIS - Correct grammar/sentencing in ath_hal(4) manual page PR: docs/54114 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> Approved by: des (mentor)
* Don't call print_pdu() when we are not debugging. This would resultharti2003-07-181-1/+2
| | | | | | | in calling fprintf() with a NULL fp. Strange enough this didn't result in cores in stable, but results in cores now. MFC after: 2 weeks
* If a proposed swap device exceeds the 8G artificial limit which outphk2003-07-181-6/+6
| | | | radix-tree code imposes, truncate the device instead of rejecting it.
* Move the implementation of the vmspace_swap_count() (used only inphk2003-07-183-64/+65
| | | | | | | | | the "toss the largest process" emergency handling) from vm_map.c to swap_pager.c. The quantity calculated depends strongly on the internals of the swap_pager and by moving it, we no longer need to expose the internal metrics of the swap_pager to the world.
* Add a new function swap_pager_status() which reports the total size of thephk2003-07-184-18/+27
| | | | | | | paging space and how much of it is in use (in pages). Use this interface from the Linuxolator instead of groping around in the internals of the swap_pager.
* Merge swap_pager.c and vm_swap.c into swap_pager.c, the separationphk2003-07-184-582/+504
| | | | | | | | | is not natural and needlessly exposes a lot of dirty laundry. Move private interfaces between the two from swap_pager.h to swap_pager.c and staticize as much as possible. No functional change.
* Correct the device identifiers for the ProATM cards.harti2003-07-181-2/+2
|
* Since checkmntlist() and getmntentry() return a struct statfs thatiedowse2003-07-181-24/+17
| | | | includes the filesystem type name, remove the "type" output parameter.
* Look for logs in the directory where we place the output.des2003-07-181-8/+9
|
* Fix taint bug in previous commit.des2003-07-181-2/+4
|
* Generate index.html in the same directory.des2003-07-181-1/+3
|
* Add some debug messages.simokawa2003-07-181-4/+6
|
* Cleanup thread accounting. Don't reset a threads timeslicedeischen2003-07-186-76/+54
| | | | | | | | when it blocks; it only gets reset when it yields. Properly set a thread's default stack guardsize. Reviewed by: davidxu
* Add a preemption point when a mutex or condition variable isdeischen2003-07-184-12/+36
| | | | | | | | | | | | | | | handed-off/signaled to a higher priority thread. Note that when there are idle KSEs that could run the higher priority thread, we still add the preemption point because it seems to take the kernel a while to schedule an idle KSE. The drawbacks are that threads will be swapped more often between CPUs (KSEs) and that there will be an extra userland context switch (the idle KSE is still woken and will probably resume the preempted thread). We'll revisit this if and when idle CPU/KSE wakeup times improve. Inspired by: Petri Helenius <pete@he.iki.fi> Reviewed by: davidxu
* Clean up KSE specific data (KSD) macros a bit.deischen2003-07-181-29/+8
| | | | Reviewed by: davidxu
* When the file system to unmount is specified by device name insteadiedowse2003-07-181-45/+7
| | | | | | | | of by mount point, umount had to take care not to unmount the wrong file system if another file system was covering the requested one. Now that the file system to unmount is specified to the kernel using the filesystem ID, this confusion cannot occur, so remove the code that checked for it.
* Obey NOCRYPTobrien2003-07-181-1/+4
| | | | Submitted by: Skip Ford <skip.ford@verizon.net>
* Make the 80x60, 132x25, 132x43, 132x50, and 132x60 VESA text modesrobert2003-07-181-0/+12
| | | | | | | | | | | work when using a graphics chipset which identifies itself as `VIA CLE266', used in some VIA EPIA boards. Two values need to be patched in the VESA mode information structure: the widths of the modes mentioned above are encoded in a format which was unknown to the VESA module (and to my copy of the VBE spec.) whereas the window memory segment values seem to be just incorrect. I tested this on a VIA EPIA-M9000 and -M10000.
* 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
OpenPOWER on IntegriCloud