summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* One of my powerbooks has this chip in it..julian2008-01-261-0/+1
| | | | | | Confirmed by looking at netbsd.. they have also added this. checked by grehen MFC After: 3 days
* Allow arbitrary baud rates, not just the standard ones.emaste2008-01-261-22/+14
|
* add opt_global.h dependencykmacy2008-01-261-1/+1
|
* Fix a harmless type error in 1.9.bde2008-01-251-1/+1
|
* Fix a bug where a thread that hit the race where the sleep timeout firesjhb2008-01-251-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | while the thread does not hold the thread lock would stop blocking for subsequent interruptible sleeps and would always immediately fail the sleep with EWOULDBLOCK instead (even sleeps that didn't have a timeout). Some background: - KSE has a facility for allowing one thread to interrupt another thread. During this process, the target thread aborts any interruptible sleeps much as if the target thread had a pending signal. Once the target thread acknowledges the interrupt, normal sleep handling resumes. KSE manages this via the TDF_INTERRUPTED flag. Specifically, it sets the flag when it sends an interrupt to another thread and clears it when the interrupt is acknowledged. (Note that this is purely a software interrupt sort of thing and has no relation to hardware interrupts or kernel interrupt threads.) - The old code for handling the sleep timeout race handled the race by setting the TDF_INTERRUPT flag and faking a KSE-style thread interrupt to the thread in the process of going to sleep. It probably should have just checked the TDF_TIMEOUT flag in sleepq_catch_signals() instead. - The bug was that the sleepq code would set TDF_INTERRUPT but it was never cleared. The sleepq code couldn't safely clear it in case there actually was a real KSE thread interrupt pending for the target thread (in fact, the sleepq timeout actually stomped on said pending interrupt). Thus, any future interruptible sleeps (*sleep(.. PCATCH ..) or cv_*wait_sig()) would see the TDF_INTERRUPT flag set and immediately fail with EWOULDBLOCK. The flag could be cleared if the thread belonged to a KSE process and another thread posted an interrupt to the original thread. However, in the more common case of a non-KSE process, the thread would pretty much stop sleeping. - Fix the bug by just setting TDF_TIMEOUT in the sleepq timeout code and not messing with TDF_INTERRUPT and td_intrval. With yesterday's fix to fix sleepq_switch() to check TDF_TIMEOUT, this is now sufficient. MFC after: 3 days
* Update the timestamp regexps in syncstamp() and monostamp() for > 99999jhb2008-01-251-2/+2
| | | | | traces where there isn't any leading whitespace before the record number in the ktrdump output.
* Backout previous commit. It's going to clutter the consolemtm2008-01-251-3/+0
| | | | | | | | | | during boot and shutdown. I think I'll hide it behind autoboot or maybe take brooks@ suggestion and implement a different command prefix for booting/shutdown purposes, but in any case it needs more thought and attention. Noticed by: ceri Pointyhat to: mtm
* Clarify in what formats the grouplist for the '-G' switch may be accepted.mtm2008-01-251-1/+1
| | | | Submitted by: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
* If the rc.conf(5) variable for a script is not enabled do not failmtm2008-01-251-0/+3
| | | | | | | | silently. Display a message that the command wasn't run and make possible suggestions for what to do. PR: conf/118770 MFC after: 1 week
* Hide ipfw internal data structures behind IPFW_INTERNAL rather thanrwatson2008-01-253-0/+16
| | | | | | | | | | exposing them to all consumers of ip_fw.h. These structures are used in both ipfw(8) and ipfw(4), but not part of the user<->kernel interface for other applications to use, rather, shared implementation. MFC after: 3 days Reported by: Paul Vixie <paul at vix dot com>
* Rev. 1.6 made it impossible to use rc.d/kerberos with the krb5 port.mtm2008-01-252-2/+1
| | | | | | | | Re-implement the change so that the script once again works with the krb5 port. Submitted by: kensmith (slightly modified) MFC after: 3 days
* Calculate baud rate divisor instead of allowing only a fixed set ofemaste2008-01-252-35/+71
| | | | | | | | | | standard rates. Obtained from OpenBSD src/sys/dev/usb/uftdi.c 1.29 src/sys/dev/usb/uftdireg.h 1.11 OpenBSD revisions noted by: ticso, on hackers
* Fix a race in the sleepqueue timeout code that resulted in sleeps notjhb2008-01-251-4/+25
| | | | | | | | | | | | | | | | | | | | | | | | | being properly cancelled by a timeout. In general there is a race between a the sleepq timeout handler firing while the thread is still in the process of going to sleep. In 6.x with sched_lock, the race was largely protected by sched_lock. The only place it was "exposed" and had to be handled was while checking for any pending signals in sleepq_catch_signals(). With the thread lock changes, the thread lock is dropped in between sleepq_add() and sleepq_*wait*() opening up a new window for this race. Thus, if the timeout fired while the sleeping thread was in between sleepq_add() and sleepq_*wait*(), the thread would be marked as timed out, but the thread would not be dequeued and sleepq_switch() would still block the thread until it was awakened via some other means. In the case of pause(9) where there is no other wakeup, the thread would never be awakened. Fix this by teaching sleepq_switch() to check if the thread has had its sleep canceled before blocking by checking the TDF_TIMEOUT flag and aborting the sleep and dequeueing the thread if it is set. MFC after: 3 days Reported by: dwhite, peter
* Once the release goes out, RELENG_7_* will need approval from so@.cperciva2008-01-241-0/+1
| | | | Approved by: core (two months ago)
* Move the code for working with kld's out into its own file.jhb2008-01-244-269/+306
|
* When asked to use kqueue, AIO stores its internal state in thedumbbell2008-01-242-4/+8
| | | | | | | | | | | | | `kn_sdata' member of the newly registered knote. The problem is that this member is overwritten by a call to kevent(2) with the EV_ADD flag, targetted at the same kevent/knote. For instance, a userland application may set the pointer to NULL, leading to a panic. A testcase was provided by the submitter. PR: kern/118911 Submitted by: MOROHOSHI Akihiko <moro@remus.dti.ne.jp> MFC after: 1 day
* Do not dereference NULL scp in the case the screen is not opened.kib2008-01-241-0/+2
| | | | | | | | Instead, return ENXIO to the ioctl caller. Reported and tested by: Pawel Worach <pawel.worach gmail com> Discussed with: markus MFC after: 3 days
* Reflect lockcount() axing and lockmgr() prototype changing.attilio2008-01-241-20/+2
|
* - sched_4bsd is no longer a default system scheduler on someru2008-01-242-13/+5
| | | | | | | | | | architectures, so call it "traditional" instead. - sched_ule is no longer buggy or experimental (according to rev. 1.7 of sched_ule(4)), so don't call it experimental (reported by a user on stable@). Reviewed by: rwatson
* Bump __FreeBSD_version in order to signal:attilio2008-01-241-1/+1
| | | | | | - lockmgr() prototype changing - lockcount() axing - LOCKMGR_ASSERT() axing
* Cleanup lockmgr interface and exported KPI:attilio2008-01-2428-177/+112
| | | | | | | | | | | | | | | | | | | | - Remove the "thread" argument from the lockmgr() function as it is always curthread now - Axe lockcount() function as it is no longer used - Axe LOCKMGR_ASSERT() as it is bogus really and no currently used. Hopefully this will be soonly replaced by something suitable for it. - Remove the prototype for dumplockinfo() as the function is no longer present Addictionally: - Introduce a KASSERT() in lockstatus() in order to let it accept only curthread or NULL as they should only be passed - Do a little bit of style(9) cleanup on lockmgr.h KPI results heavilly broken by this change, so manpages and FreeBSD_version will be modified accordingly by further commits. Tested by: matteo
* There is no PUC_FASTINTR option anymore.marck2008-01-241-12/+1
| | | | MFC after: 2 weeks
* - Reduce how much ZFS caches by default. This is another change to mitigatepjd2008-01-242-8/+10
| | | | | | | 'kmem_map too small panics'. - Print two warnings if there is not enough memory and not enough address space. - Improve comment.
* Change type of kmem_used() and kmem_size() functions to uint64_t, so itpjd2008-01-244-12/+12
| | | | | | | | | | | | | doesn't overflow in arc.c in this check: if (kmem_used() > (kmem_size() * 4) / 5) return (1); With this bug ZFS almost doesn't cache. Only 32bit machines are affected that have vm.kmem_size set to values >=1GB. Reported by: David Taylor <davidt@yadt.co.uk>
* Replace the last susers calls in netinet6/ with privilege checks.bz2008-01-248-68/+99
| | | | | | | | | Introduce a new privilege allowing to set certain IP header options (hop-by-hop, routing headers). Leave a few comments to be addressed later. Reviewed by: rwatson (older version, before addressing his comments)
* Differentiate between addifaddr and delifaddr for the privilege check.bz2008-01-241-1/+2
| | | | | Reviewed by: rwatson MFC after: 2 weeks
* Remove one more alpha leftover.ru2008-01-241-1/+1
|
* Many improvements that have been collected over time:scottl2008-01-243-43/+146
| | | | | | - Improve error handling for load operations. - Fix a memory corruption bug when using certain linux management apps. - Allocate all commands up front to avoid OOM deadlocks later on.
* Flag a hack.ru2008-01-241-1/+2
|
* Style.ru2008-01-241-2/+2
|
* Shorter equivalent of the command.ru2008-01-241-1/+1
|
* Cosmetique: sort the list.ru2008-01-241-2/+2
|
* Add a diagnostic note about "transmission error ... tx underrun, increasingtrhodes2008-01-241-1/+6
| | | | | | | | | tx start threshold ..." Looking around on the mailing lists, and even having one of these cards I agree the messages should be documented. Bump doc date. PR: 88477
* Support source upgrades from at least 6.0-RELEASE.ru2008-01-232-5/+6
| | | | Reviewed by: imp, obrien
* tcp_usrreq.c:1.313 removed tcbinfo locking from tcp_usr_accept(), whichrwatson2008-01-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | while in principle a good idea, opened us up to a race inherrent to the syncache's direct insertion of incoming TCP connections into the "completed connection" listen queue, as it transpires that the socket is inserted before the inpcb is fully filled in by syncache_expand(). The bug manifested with the occasional returning of 0.0.0.0:0 in the address returned by the accept() system call, which occurred if accept managed to execute tcp_usr_accept() before syncache_expand() had copied the endpoint addresses into inpcb connection state. Re-add tcbinfo locking around the address copyout, which has the effect of delaying the copy until syncache_expand() has finished running, as it is run while the tcbinfo lock is held. This is undesirable in that it increases contention on tcbinfo further, but a more significant change will be required to how the syncache inserts new sockets in order to fix this and keep more granular locking here. In particular, either more state needs to be passed into sonewconn() so that pru_attach() can fill in the fields *before* the socket is inserted, or the socket needs to be inserted in the incomplete connection queue until it is actually ready to be used. Reported by: glebius (and kris) Tested by: glebius
* Fix a regression introduced in rev 1.99: replace fclose(f) with a commentdes2008-01-231-1/+5
| | | | | | explaining why f cannot possibly be a valid FILE * at this point. MFC after: 1 day
* - Document firewall_nat_enable related settings.chinsan2008-01-231-1/+26
| | | | | Tested by: AB MFC after: 1 month
* Fix bundle xmit octets stats for packet-split operation mode.mav2008-01-231-4/+4
|
* o Add boot, gdb, nfsserver and opencrypto dirs to CSCOPEDIRS; sort.maxim2008-01-231-3/+3
|
* Track version # from the portable release.kientzle2008-01-231-1/+1
|
* Explain a subtle API change that was made recently.kientzle2008-01-231-0/+21
| | | | | | Even though I believe this is a good change, it does have the potential to break certain clients, so it's good to document the reasoning behind the change.
* Properly pad symlinks when writing cpio "newc" format.kientzle2008-01-232-4/+49
| | | | | Thanks to: Jesse Barker for reporting this. MFC after: 7 days
* "NONE" -> "ASCII" encodingache2008-01-231-1/+1
|
* - sched_prio() should only adjust tdq_lowpri if the thread is running or onjeff2008-01-231-7/+9
| | | | | | | | a run-queue. If the priority is numerically raised only change lowpri if we're certain it will be correct. Some slop is allowed however previously we could erroneously raise lowpri for an idle cpu that a thread had recently run on which lead to errors in load balancing decisions.
* Fix longstanding mb/wc functions segfault if error occurseache2008-01-231-29/+39
| | | | | inside _<encoding>_init(). Currently _EUC_init() only was affected.
* Better fix for longstanding segfault. Don't touch current locale at allache2008-01-231-17/+29
| | | | on unknown encoding. Previous fix resets it to POSIX.
* 1) Add (void) cast to _none_init() (while I am here)ache2008-01-231-2/+4
| | | | | 2) Fix longstanding segfault in mb/wc code when unknown encoding is specified in the locale file (mb/wc functions becomes NULL in that case).
* Conditionally add mklocale to bootstrap-toolsache2008-01-231-0/+5
|
* Bump FreeBSD_version after adding "ASCII" encoding to libcache2008-01-231-1/+1
|
* Take advantage of the new physically contiguous 9K jumbos in 8.gallatin2008-01-222-3/+29
|
OpenPOWER on IntegriCloud