summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Assume that "" passed as parameter also means "no grouping"phantom2001-02-121-3/+4
| | | | Make comparsions more clear (per style(9))
* Rewrite __time_load_locale() using ldpart.c::__part_load_locale()phantom2001-02-122-153/+15
| | | | Reviewed by: ache
* Use .Rv macro instead of hardcoded messagephantom2001-02-121-6/+1
|
* Print out sensekey specifik values if set on errorsos2001-02-121-3/+8
|
* Properly report the VIA '586 type.sos2001-02-121-1/+3
|
* "Cross references in the SEE ALSO section should be sorted by sectionru2001-02-121-2/+2
| | | | | number, and then placed in alphabetical order and comma separated.", mdoc.samples(7) said.
* mmap(3) -> mmap(2).ru2001-02-121-2/+2
|
* Added the KME SCSI-CARD-001 of a SCSI card (accessory oftoshi2001-02-121-0/+4
| | | | | | | Hewlett Packard M820e CD-writer). Pointed out by: mitchy@er.ams.eng.osaka-u.ac.jp Submitted by: Stacy Millions <stacy@millions.ca>
* Patches backported from later development version of OpenSSH which preventkris2001-02-125-28/+53
| | | | | | | | (instead of just mitigating through connection limits) the Bleichenbacher attack which can lead to guessing of the server key (not host key) by regenerating it when an RSA failure is detected. Reviewed by: rwatson
* Fix `make depend' => `make kernel-depend'. Using the dependancy fileobrien2001-02-125-5/+25
| | | | when rebuilding it is just Wrong.
* Give some additional DNS black hole possibilities as comments.gshapiro2001-02-121-1/+3
| | | | Submitted by: clive
* It sounded like a good idea at the time. The previous change breakspeter2001-02-122-10/+3
| | | | | FILE *buffer = stdout; so back it out for now.
* Change all instances of `CURPROC' and `CURTHD' to `curproc,' in orderbmilekic2001-02-124-45/+45
| | | | | | to stay consistent. Requested by: bde
* Catch up to mutex API changes.bmilekic2001-02-121-145/+214
|
* Take advantage of the current libc sizeof(FILE) breakage (__sF[]) andpeter2001-02-122-3/+10
| | | | | | | | | | try a hopefully more robust stdin/stdout/stderr. This costs an indirect pointer fetch, but saves us from changes in 'FILE'. The __stdin stuff is there to not pollute application name space if the application does not use <stdio.h> and also in case something depended on the current behavior where stdin etc was a #define. Reviewed by: eischen, dillon
* o Fix build of libc broken in revision 1.2. offsetof() requires therwatson2001-02-121-0/+2
| | | | | | inclusion of stddef.h. Reviewed by: peter
* Note that packets read as outgoing have invalid IP header checksums.archie2001-02-121-0/+1
|
* Catch up to new priority interface.jake2001-02-125-27/+25
|
* Implement a unified run queue and adjust priority levels accordingly.jake2001-02-1239-554/+581
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - All processes go into the same array of queues, with different scheduling classes using different portions of the array. This allows user processes to have their priorities propogated up into interrupt thread range if need be. - I chose 64 run queues as an arbitrary number that is greater than 32. We used to have 4 separate arrays of 32 queues each, so this may not be optimal. The new run queue code was written with this in mind; changing the number of run queues only requires changing constants in runq.h and adjusting the priority levels. - The new run queue code takes the run queue as a parameter. This is intended to be used to create per-cpu run queues. Implement wrappers for compatibility with the old interface which pass in the global run queue structure. - Group the priority level, user priority, native priority (before propogation) and the scheduling class into a struct priority. - Change any hard coded priority levels that I found to use symbolic constants (TTIPRI and TTOPRI). - Remove the curpriority global variable and use that of curproc. This was used to detect when a process' priority had lowered and it should yield. We now effectively yield on every interrupt. - Activate propogate_priority(). It should now have the desired effect without needing to also propogate the scheduling class. - Temporarily comment out the call to vm_page_zero_idle() in the idle loop. It interfered with propogate_priority() because the idle process needed to do a non-blocking acquire of Giant and then other processes would try to propogate their priority onto it. The idle process should not do anything except idle. vm_page_zero_idle() will return in the form of an idle priority kernel thread which is woken up at apprioriate times by the vm system. - Update struct kinfo_proc to the new priority interface. Deliberately change its size by adjusting the spare fields. It remained the same size, but the layout has changed, so userland processes that use it would parse the data incorrectly. The size constraint should really be changed to an arbitrary version number. Also add a debug.sizeof sysctl node for struct kinfo_proc.
* 1. The key SSD_KEY_RECOVERED_ERROR is not an error at all and shouldmjacob2001-02-111-7/+15
| | | | | | | | | | | | | | | | | | | | not be retried. It is an indication that there was an error that was corrected during the execution of the command. This is per ANSI SCSI2 spec. It's possible that these should also be noted to the console (as indicative, perhaps, of growing media defect lists in drives), but the default of printing errors out if bootverbose in this case is probably enough. Also, there'd been a missing ERESTART for that clause anyway. 2. If you have an ABORTED COMMAND, it's almost invariably a SCSI parity error. You should never be silent about these since users should do something about this if it occurs (moving that power cord *away* from the SCSI cable is always a good first start). This should print irrespective of bootverbose because it's an actual real error even if we retry a transmission. Reviewed by: audit@freebsd.org, gibbs@freebsd.org
* Remove (int) file descriptor locking. It should be up to thedeischen2001-02-1111-512/+59
| | | | | | | | | | | | | application to provide locking for I/O operations. This doesn't break any of my tests, but the old behavior can be restored by compiling with _FDLOCKS_ENABLED. This will eventually be removed when it is obvious it does not cause any problems. Remove most of flockfile implementation, with the exception of flockfile_debug. Make error messages more informational (submitted by Mike Heffner <spock@techfour.net>, who's now known as mikeh@FreeBSD.org).
* libc MT-safety, part 2.deischen2001-02-1122-104/+261
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add a lock to FILE. flockfile and friends are now implemented (for the most part) in libc. flockfile_debug is implemented in libc_r; I suppose it's about time to kill it but will do it in a future commit. Fix a potential deadlock in _fwalk in a threaded environment. A file flag (__SIGN) was added to stdio.h that, when set, tells _fwalk to ignore it in its walk. This seemed to be needed in refill.c because each file needs to be locked when flushing. Add a stub for pthread_self in libc. This is needed by flockfile which is allowed by POSIX to be recursive. Make fgetpos() error return value (-1) match man page. Remove recursive calls to locked functions (stdio); I think I've got them all, but I may have missed a couple. A few K&R -> ANSI conversions along with removal of a few instances of "register". $Id$ -> $FreeBSD$ in libc/stdio/rget.c Not objected to: -arch, a few months ago
* libc MT-safety, part 2.deischen2001-02-111-0/+4
| | | | Add a lock to FILE and define an additional flag.
* Uname is in section 3 of the manual pages.dwmalone2001-02-111-1/+1
| | | | | PR: 25008 Submitted by: fullermd@over-yonder.net
* Mention PROT_NONE in the list of possible protections.nik2001-02-111-0/+2
| | | | Pointed out by: kris
* Include mmap(2) in the list of memory allocation functions.nik2001-02-111-2/+10
| | | | Reviewed by: hackers
* .Xr to mmap.nik2001-02-111-1/+2
|
* Note that mmap(2) can allocate memory, as well as mapping existing files,nik2001-02-111-1/+1
| | | | | | in the .Nd. Reviewed by: hackers
* LSI/SYMBIOS/NCR 53C[8XX|10XX] supported hardware updated.groudier2001-02-111-4/+6
| | | | (One may check if the 8 words added are correct english :) )
* Add a man page for the dbm_* functions, and update the Makefile to linknik2001-02-112-1/+211
| | | | | | | | | | it in. Some review from -hackers (some time ago), and I think the best way to get this improved (if it needs improving) or updating, is to bring it in. PR: docs/12557 Submitted by: Tim Singletary <tsingle@triana.gsfc.nasa.gov>
* Make a big improvement to entropy-harvesting speed by not having anymarkm2001-02-112-66/+41
| | | | locks (only atomic assigns) in the harvest ringbuffer.
* Add ja_JP.EUC locale support for LC_MESSAGES, LC_MONETARY, and LC_NUMERIC.knu2001-02-119-3/+122
|
* Add ko_KR.EUC locale support for LC_MESSAGES, LC_MONETARY, and LC_NUMERIC.asmodai2001-02-119-3/+122
| | | | Submitted by: CHOI Junho <cjh@kr.FreeBSD.org>
* Fix:groudier2001-02-111-10/+32
| | | | | | | | | | | | | | | | | - Missing cpu_to_scr() added (endian-ness). Improvement (fix|workaroung??): - Blindly firing a PPR can lead to some messy situations due to various causes or misfeatures, for example: * The 53C1010-[33|66] supports offset 62 in DT mode, but only offset 31 in ST mode. As a result, a PPR(DT, offset 62) responded with PPR(ST, any offset > 31) must be rejected. * A device that doesn't know about PPR should reject it, but may also be confused by this message. When a PPR encounters problems, the driver now patches the goal transfer settings for legacy negotiations to be performed later with the offending target. This give a chance for bad situations to be fixed automagically.
* Don't use hardcoded struct size, use offsetof() instead (make size calculationsphantom2001-02-111-5/+7
| | | | dynamic)
* Don't try to convert grouping strings in case if C or POSIX localephantom2001-02-112-2/+2
| | | | | | was explicitly specified. Submitted by: ache
* RIP <machine/lock.h>.markm2001-02-1139-295/+159
| | | | | | | Some things needed bits of <i386/include/lock.h> - cy.c now has its own (only) copy of the COM_(UN)LOCK() macros, and IMASK_(UN)LOCK() has been moved to <i386/include/apic.h> (AKA <machine/apic.h>). Reviewed by: jhb
* Clean up RST ratelimiting. Previously, ratelimiting occured before testsbmilekic2001-02-115-78/+109
| | | | | | | | | | | were performed to determine if the received packet should be reset. This created erroneous ratelimiting and false alarms in some cases. The code has now been reorganized so that the checks for validity come before the call to badport_bandlim. Additionally, a few changes in the symbolic names of the bandlim types have been made, as well as a clarification of exactly which type each RST case falls under. Submitted by: Mike Silbersack <silby@silby.com>
* Long awaited style fixup in mbuf code. Get rid of K&R style prototypingbmilekic2001-02-113-187/+136
| | | | | | and function argument declarations. Make sure that functions that are supposed to return a pointer return NULL in case of failure. Don't cast NULL. Finally, get rid of annoying `register' uses.
* Eliminate ISP2100_FABRIC- we always allow for fabric now. Add anmjacob2001-02-111-19/+86
| | | | | | | | | isp_iid_set/isp_iid for fibre channel- this is because we now fake a port database entry for ourselves. Add the additional loop states between LOOP_PDB_RCVD and LOOP_READY. Change and comment on a wad of Fibre Channel isp_control functions. Change and comment on some of the ISPASYNC Fibre Channel events.
* Add structure defining FC-AL position maps. The only tool that I know ofmjacob2001-02-111-0/+16
| | | | that really uses this is luxadm(8) under Solaris.
* Shuffle around how we do isp_disable management- make sure we return 0 somjacob2001-02-111-21/+25
| | | | | | | | | the unit number doesn't get reused. Make sure that if we've compiled for ISP_TARGET_MODE we set the default role to be ISP_ROLE_INITIATOR|ISP_ROLE_TARGET. Do some misc other cleanups.
* Add isp_fc_runstate function- this function's purpose is to, in stages,mjacob2001-02-111-0/+54
| | | | | | | | and depending on role, make sure link is up, scan the fabric (if we're connected to a fabric), scan the local loop (if appropriate), merge the results into the local port database then, check once again to make sure we have f/w at FW_READY state and the the loopstate is LOOP_READY.
* Default the plist dir as we know where it is relative to us.obrien2001-02-111-19/+9
|
* Minor comment & doc tweak.obrien2001-02-111-2/+4
|
* Roll minor version. Remove ISP2100_FABRIC define (unneeded now).mjacob2001-02-111-2/+6
| | | | | | | Comment out usage of ISP_SMPLOCK- I have my doubts that this works sanely as yet because CAM itself still needs Giant. I *was* dropping my lock and grabbing Giant when doing the upcall for completion, but this is all seems ridiculous until CAM is fixed.
* Do some cleanup based upon adapter role- mainly not enabling interruptsmjacob2001-02-111-35/+33
| | | | | | | | | | | if we're ISP_ROLE_NONE. Change ISPASYNC_LOGGED_INOUT to ISPASYNC_PROMENADE. Make sure we note if something is a fabric device. Target mode: Finally fix (to a first approximation) SCSI Target Mode again- we needed to correctly check against CAM_TARGET_WILDCARD and CAM_LUN_WILDCARD so that targbh won't confuse us. Comment out the drainqueue stuff for now. Use isp_fc_runstate instead if isp_control/ISPCTL_FCLINK_TEST.
* Minor stuff:mjacob2001-02-111-370/+593
| | | | | | | | | | | | | | | | | | | | | | | Remove ISP2100_FABRIC defines- we always handle fabric now. Insert isp_getmap helper function (for getting Loop Position map). Make sure we (for our own benefit) mark req_state_flags with RQSF_GOT_SENSE for Fibre Channel if we got sense data- the !*$)!*$)~*$)*$ Qlogic f/w doesn't do so. Add ISPCTL_SCAN_FABRIC, ISPCTL_SCAN_LOOP, ISPCTL_SEND_LIP, and ISPCTL_GET_POSMAP isp_control functions. Correctly send async notifications upstream for changes in the name server, changes in the port database, and f/w crashes. Correctly set topology when we get a ASYNC_PTPMODE event. Major stuff: Quite massively redo how we handle Loop events- we've now added several intermediate states between LOOP_PDB_RCVD and LOOP_READY. This allows us a lot finer control about how we scan fabric, whether we go further than scanning fabric, how we look at the local loop, and whether we merge entries at the level or not. This is the next to last step for moving managing loop state out of the core module entirely (whereupon loop && fabric events will simply freeze the command queue and a thread will run to figure out what's changed and *it* will re-enable the queu). This fine amount of control also gets us closer to having an external policy engine decide which fabric devices we really want to log into.
* update to latest and greatest f/wmjacob2001-02-115-11570/+13592
|
* - Place back STR string declarations for lock/unlock strings used for KTR_LOCKbmilekic2001-02-114-45/+92
| | | | | | | | | | | | | | | tracing in order to avoid duplication. - Insert some tracepoints back into the mutex acq/rel code, thus ensuring that we can trace all lock acq/rel's again. - All CURPROC != NULL checks are MPASS()es (under MUTEX_DEBUG) because they signify a serious mutex corruption. - Change up some KASSERT()s to MPASS()es, and vice-versa, depending on the type of problem we're debugging (INVARIANTS is used here to check that the API is being used properly whereas MUTEX_DEBUG is used to ensure that something general isn't happening that will have bad impact on mutex locks). Reminded by: jhb, jake, asmodai
OpenPOWER on IntegriCloud