summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add a quirk for ciss to stop trying to read the serial number offps2004-06-211-0/+5
| | | | of logical volumes.
* PR: docs/67884mpp2004-06-211-1/+1
| | | | Submitted by: Chirstopger Nehren <apeiron@comcast.net>
* This should be the right set of docs sources.obrien2004-06-211-3/+5
|
* Add manual pages for cm(4), esp(4), rc(4) and snc(4).trhodes2004-06-215-0/+595
|
* MFCronyx: add cross-references, fix history section.rik2004-06-213-10/+17
|
* Disable building of GDB info files until the gdb6 upgrade is finished.obrien2004-06-212-2/+8
|
* Turned off the "calcru: negative time" warning for certain SMP casesbde2004-06-211-12/+34
| | | | | | | | | | | where it is known to detect a problem but the problem is not very easy to fix. The warning became very common recently after a call to calcru() was added to fill_kinfo_thread(). Another (much older) cause of "negative times" (actually non-monotonic times) was fixed in rev.1.237 of kern_exit.c. Print separate messages for non-monotonic and negative times.
* Spelling fixes.mpp2004-06-2120-44/+44
|
* Have `ps' return the cputimes for zombies, with the assumption thatgad2004-06-211-1/+1
| | | | | | | kvm_getprocs() will provide useful information if it can, or *it* will provide a zero value if it can not find something appropriate. Submitted by: bde
* Use the correct type (lwpid_t) for ki_tid .gad2004-06-211-1/+1
| | | | | Noticed by: julian Approved by: julian, marcel
* Fixed style bugs in previous commit (151 characters of trailing whitespace).bde2004-06-211-1/+1
|
* libcompat doesn't seem to be needed any more.phk2004-06-211-2/+2
|
* libcompat doesn't seem to be necessary any more.phk2004-06-211-3/+0
|
* Discontinue use of old libcompat regexp routines.phk2004-06-212-51/+12
|
* MFcx(4) 1.23: markup fixes by ru@.rik2004-06-212-13/+17
|
* Initialize $timeout to 0.des2004-06-211-0/+1
|
* Spelling fixes.mpp2004-06-214-4/+4
|
* (1) Removed the bogus condition "p->p_pid != 1" on calling sched_exit()bde2004-06-211-7/+1
| | | | | | | | | | | | | | | | | | | | | from exit1(). sched_exit() must be called unconditionally from exit1(). It was called almost unconditionally because the only exits on system shutdown if at all. (2) Removed the comment that presumed to know what sched_exit() does. sched_exit() does different things for the ULE case. The call became essential when it started doing load average stuff, but its caller should not know that. (3) Didn't fix bugs caused by bitrot in the condition. The condition was last correct in rev.1.208 when it was in wait1(). There p was spelled curthread->td_proc and was for the waiting parent; now p is for the exiting child. The condition was to avoid lowering init's priority. It should be in sched_exit() itself. Lowering of priorities is broken in other ways in at least the 4BSD scheduler, and doing it for init causes less noticeable problems than doing it for for shells. Noticed by: julian (1)
* Add a timeout after which tinderbox(1) will kill its children and exit.des2004-06-214-3/+36
|
* Spelling fixes.mpp2004-06-212-2/+2
|
* Spelling fixes.mpp2004-06-211-3/+3
|
* Spelling fixes.mpp2004-06-2114-21/+21
|
* Update p_runtime on exit. This fixes calcru() on zombies, and preparesbde2004-06-211-2/+9
| | | | | | | for not calling calcru() on exit. calcru() on a zombie can happen if ttyinfo() (^T) picks one. PR: 52490
* Prevent the rp driver from panic'ing on first access and make atgallatin2004-06-213-29/+33
| | | | | | | | | | | | | | | | | | | least the pci device unloadable - Use ttymalloc() rather than a plain malloc to allocate the rp->rp_tty ttys. This is now required due to the recent locking changes to ttys and prevents a panic due to locking an unitialized t_mtx. - Allow the pci driver to be unloaded. This involved moving the call rp_releaseresource() to the end of rp_pcireleaseresource(), since rp_pcireleaseresource() uses ctlp->dev, which is freed by rp_releaseresource(). - Allow the generic part of the driver to be unattached by providing a hook to cancel timeouts. Glanced at by: obrien
* New style functions, kill register keyword.phk2004-06-211-43/+28
|
* Call tzset() at startup.brian2004-06-211-0/+3
| | | | Submitted by: Andrzej ToboÅa <ato@iem.pw.edu.pl>
* Print mediasize in human readable form as well.pjd2004-06-213-5/+10
|
* Don't hold topology lock while calling g_gate_release().pjd2004-06-211-0/+2
| | | | Found by: KASSERT()
* - Missing trailing slash for a kern directory check.pjd2004-06-211-3/+5
| | | | | | | - Check in both places if ${_dir}/conf/kmod.mk exists. - Style fixes (lines too long). Submitted by: bde
* o Reduce path names in RRQ and WRQ packets by:brian2004-06-211-2/+34
| | | | | | | | | | | | | | | | | Reducing "/+./" strings to "/" Reducing "/[^/]+/../" to "/" o Don't send an OACK when the result of the [RW]RQ is an error. These changes allow tftpd to interact with pxelinux.bin from the syslinux package. Whilst the path reducing code doesn't properly handle situations where the path component before the "/../" is a symlink to (say) ".", I would suggest that it does the right thing in terms of the clients perception of what their path string actually represents. This seems better than using realpath() and breaking environments where symlinks point outside of the directory hierarchy that tftpd is configured to allow.
* Include module.hscottl2004-06-211-0/+1
| | | | Submitted by: Koop Mast
* Extend the description of SIOC[GS]IFCAP.yar2004-06-211-5/+14
|
* Merge next step in socket buffer locking:rwatson2004-06-216-69/+558
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - sowakeup() now asserts the socket buffer lock on entry. Move the call to KNOTE higher in sowakeup() so that it is made with the socket buffer lock held for consistency with other calls. Release the socket buffer lock prior to calling into pgsigio(), so_upcall(), or aio_swake(). Locking for this event management will need revisiting in the future, but this model avoids lock order reversals when upcalls into other subsystems result in socket/socket buffer operations. Assert that the socket buffer lock is not held at the end of the function. - Wrapper macros for sowakeup(), sorwakeup() and sowwakeup(), now have _locked versions which assert the socket buffer lock on entry. If a wakeup is required by sb_notify(), invoke sowakeup(); otherwise, unconditionally release the socket buffer lock. This results in the socket buffer lock being released whether a wakeup is required or not. - Break out socantsendmore() into socantsendmore_locked() that asserts the socket buffer lock. socantsendmore() unconditionally locks the socket buffer before calling socantsendmore_locked(). Note that both functions return with the socket buffer unlocked as socantsendmore_locked() calls sowwakeup_locked() which has the same properties. Assert that the socket buffer is unlocked on return. - Break out socantrcvmore() into socantrcvmore_locked() that asserts the socket buffer lock. socantrcvmore() unconditionally locks the socket buffer before calling socantrcvmore_locked(). Note that both functions return with the socket buffer unlocked as socantrcvmore_locked() calls sorwakeup_locked() which has similar properties. Assert that the socket buffer is unlocked on return. - Break out sbrelease() into a sbrelease_locked() that asserts the socket buffer lock. sbrelease() unconditionally locks the socket buffer before calling sbrelease_locked(). sbrelease_locked() now invokes sbflush_locked() instead of sbflush(). - Assert the socket buffer lock in socket buffer sanity check functions sblastrecordchk(), sblastmbufchk(). - Assert the socket buffer lock in SBLINKRECORD(). - Break out various sbappend() functions into sbappend_locked() (and variations on that name) that assert the socket buffer lock. The !_locked() variations unconditionally lock the socket buffer before calling their _locked counterparts. Internally, make sure to call _locked() support routines, etc, if already holding the socket buffer lock. - Break out sbinsertoob() into sbinsertoob_locked() that asserts the socket buffer lock. sbinsertoob() unconditionally locks the socket buffer before calling sbinsertoob_locked(). - Break out sbflush() into sbflush_locked() that asserts the socket buffer lock. sbflush() unconditionally locks the socket buffer before calling sbflush_locked(). Update panic strings for new function names. - Break out sbdrop() into sbdrop_locked() that asserts the socket buffer lock. sbdrop() unconditionally locks the socket buffer before calling sbdrop_locked(). - Break out sbdroprecord() into sbdroprecord_locked() that asserts the socket buffer lock. sbdroprecord() unconditionally locks the socket buffer before calling sbdroprecord_locked(). - sofree() now calls socantsendmore_locked() and re-acquires the socket buffer lock on return. It also now calls sbrelease_locked(). - sorflush() now calls socantrcvmore_locked() and re-acquires the socket buffer lock on return. Clean up/mess up other behavior in sorflush() relating to the temporary stack copy of the socket buffer used with dom_dispose by more properly initializing the temporary copy, and selectively bzeroing/copying more carefully to prevent WITNESS from getting confused by improperly initialized mutexes. Annotate why that's necessary, or at least, needed. - soisconnected() now calls sbdrop_locked() before unlocking the socket buffer to avoid locking overhead. Some parts of this change were: Submitted by: sam Sponsored by: FreeBSD Foundation Obtained from: BSD/OS
* Add the `-O emul' format option, which prints the name of the system-callgad2004-06-203-0/+13
| | | | | | | | emulation environment the process is in. "emul" as a keyword is picked up from OpenBSD. PR: bin/65803 Submitted by: Cyrille Lefevre
* Fix the following error:marcel2004-06-201-0/+2
| | | | | | | | | | | | | | ld: locore.o: non-pic code with imm relocation against dynamic symbol `__gp' With binutils 2.15, ld(1) defines the implicit/automatic symbol __gp as a dynamic symbol and thus will now complain when used in a non-PIC fashion (the immediate relocation used to set the GP register). Resolve this by defining __gp in the linker script. Make sure __gp is aligned on a 16-byte boundary. Note: the 0x200000 magic offset is due to having a 22-bit GP-relative relocation. The GOT will be accessed with negative offsets from GP.
* From SUSv3:gad2004-06-201-1/+1
| | | | | | | | | | | Any [standard output] field need not be meaningful in all implementations. In such a case a hyphen ('-') should be output in place of the field value So have the `-O label' option print out the string " -" if the process has no label. Approved by: Silence from rwatson and green (when asked in March...)
* Add new output-format keywords of LWP and NLWP, which show the thread-idgad2004-06-201-0/+8
| | | | | | | | | | and number-of-threads tied to a process. Result can be seen by typing, e.g.: ps -HO lwp,nlwp These new options are not documented yet. More options will be coming, and I will update the man page after I get farther along. PR: bin/65803 (though adjusted to fit our present source) Submitted by: Cyrille Lefevre
* Fill in the values for the ki_tid and ki_numthreads which have beengad2004-06-201-0/+2
| | | | | | | added to kproc_info. PR: bin/65803 (a tiny part...) Submitted by: Cyrille Lefevre
* Change the architecture-based setting of KINFO_PROC_SIZE and KI_NSPARE sogad2004-06-201-14/+32
| | | | | | | | | that it is a series of alphabetically-ordered #fidef's, from Bruce Evans. Define two new thread-related values in kproc_info, from Cyrille Lefevre. Also remove a few values from kproc_info that were not needed, and change around a few comments, from me. Changes are combined into a single commit simply because it is a hassle to make sure that alignments and sizes are not changed on any platform when modifying kproc_info.
* Include an annotation of NET_{LOCK,UNLOCK}_GIANT() noting that theserwatson2004-06-201-1/+4
| | | | | calls do not have the same recursion semantics as DROP_GIANT and PICKUP_GIANT.
* It's now the responsibility of the consumer of soabort() to remove arwatson2004-06-201-1/+12
| | | | | | | socket from its accept queue when aborting it during a new inbound connection. Update spx_input() to acquire the accept lock, assert the condition of the socket on its parent queue, and approriately disconnect it from the queue before calling soabort() on it.
* If debug.mpsafenet is set, initialize TCP callouts as CALLOUT_MPSAFE.rwatson2004-06-202-10/+24
|
* In uipc_rcvd(), lock the socket buffers at either end of the UNIXrwatson2004-06-201-0/+4
| | | | | | | domain sokcet when updating fields at both ends. Submitted by: sam Sponsored by: FreeBSD Foundation
* Merge changes from the tzcode2004a import.stefanf2004-06-205-51/+89
|
* Annotate so_state as locked with SOCK_LOCK(so).rwatson2004-06-201-1/+4
| | | | Add a commenting indicating that the SB_ constants apply to sb_flags.
* Hold SOCK_LOCK(so) when frobbing so_state when disconnecting arwatson2004-06-201-1/+5
| | | | connected UNIX domain datagram socket.
* Have the main() routine calculate %CPU and (if needed) memory informationgad2004-06-202-36/+31
| | | | | | | when copying per-process info before starting to sort the list. This way, sort-by-CPU or sort-by-memory will only calculate values once-per-process, instead of twice-per-comparison. Also take advantage of this to simplify the pscomp() routine.
* Remove one more unneeded reference to arpcom.ac_netgraph.wpaul2004-06-201-10/+34
| | | | | | | | | | | | | | | | Tweak things so that ng_fec has a chance of working with things other than ethernet. Use ifp->if_output of the underlying interfaces and use IF_HANDOFF() rather than depending on ether_output() and ether_output_frame() explicitly. Also, don't insist that underlying devices be IFM_ETHER when checking their link states in the link monitor code. With these changes, I was able to create a two channel bundle consisting of one ethernet interface and one 802.11 wireless device (via ndis). Note that this only works because both devices use the same if_output vector: ng_fec will not let you bundle devices with different output vectors together (it really doesn't make sense to do that).
* - Simplify pmap_remove_pages(), eliminating unnecessary indirection.alc2004-06-202-25/+24
| | | | | - Simplify the locking of pmap_is_modified() by converting control flow to data flow.
* Remove from HEAD, that what is not on the vendor branch anymore.marcel2004-06-201-291/+0
|
OpenPOWER on IntegriCloud