summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix some text messages.davidxu2004-08-221-2/+2
|
* Part 2 of fixing the boot code: gcc 3.4 fixes.marcel2004-08-222-2/+2
| | | | | | | | | The whole problem seems to be size. Which is odd, because it is said that size doesn't matter. Anyway... Add -Os to strategic places in the makefile to have the final loader be as mall as possible. This seems to be enough to make it work. For now... I think something is more fundamentally wrong; or something more fundamental is wrong. Potato, potaato.
* Add code to support statically linked binary and .core file of threadeddavidxu2004-08-221-177/+367
| | | | program.
* Found another one. Why does mdconfig hate me? Add a "sleep 5" tokensmith2004-08-221-0/+2
| | | | | | | | | | | this script, without it sparc64 ISO building was consistently failing because the /dev/md0 device name was not present when the commands following mdconfig ran. Apparently there is the possibility of a delay between when mdconfig finishes and the names become visible in /dev. Yes, we could code this better than an unconditional call to "sleep 5" but IMHO we should fix the underlying problem instead. MFC after: 3 days
* diff reduction for upcoming patch. Use a macro that masksjulian2004-08-221-8/+9
| | | | | some of the odd goings on with sub-structures, because they will go away anyhow.
* Add support for Intel E7205 AGP.anholt2004-08-222-0/+12
| | | | | PR: kern/69858 Submitted by: Jacobo Arvelo <unix4all at gulic dot org>
* Currently, if the secure level is low enough, system flags cancsjp2004-08-221-1/+1
| | | | | | | | | | | | | | | | | | | be manipulated by prison root. In 4.x prison root can not manipulate system flags, regardless of the security level. This behavior should remain consistent to avoid any surprises which could lead to security problems for system administrators which give out privileged access to jails. This commit changes suser_cred's flag argument from SUSER_ALLOWJAIL to 0. This will prevent prison root from being able to manipulate system flags on files. This may be a MFC candidate for RELENG_5. Discussed with: cperciva Reviewed by: rwatson Approved by: bmilekic (mentor) PR: kern/70298
* When sliding the m_data pointer forward, update m_pktrhdr.len as wellrwatson2004-08-221-1/+3
| | | | | | | | | as m_len, or the pkthdr length will be inconsistent with the actual length of data in the mbuf chain. The symptom of this occuring was "out of data" warnings from in_cksum_skip() on large UDP packets sent via the loopback interface. Foot shot: green
* Part 1 of fixing the boot code: binutils 2.15 fixes.marcel2004-08-222-1/+202
| | | | | | | | | | | | The binutils 2.15 assembler now automaticly and non-optionally adds the .eh_frame section for unwind information. This section appears to wreck havoc to the final boot code. Fix this by using a special linker script that discards the .eh_frame sections, but is otherwise identical to the linker internal script used for -N. Compiler used: gcc 3.3.5 Verified with: binutils 2.14 & binutils 2.15 (stock and in-tree) Tested with: /boot/loader & /boot/netboot
* In the previous revision, I failed to condition an early release of Giantalc2004-08-221-1/+2
| | | | | | | in vm_fault() on debug_mpsafevm. If debug_mpsafevm was not set, the result was an assertion failure early in the boot process. Reported by: green@
* If a tunable for the routing socket netisr queue max is defined, allow itrwatson2004-08-211-1/+3
| | | | | to override the default value, rather than the default value overriding the tunable.
* Allow the size of the routing socket netisr queue to be configured usingrwatson2004-08-211-1/+6
| | | | | | | | | | the tunable or sysctl 'net.route.netisr_maxqlen'. Default the maximum depth to 256 rather than IFQ_MAXLEN due to the downsides of dropping routing messages. MT5 candidate. Discussed with: mdodd, mlaier, Vincent Jardin <jardin at 6wind.com>
* Add version history.pjd2004-08-211-0/+5
|
* Protect the period! And add a new line.trhodes2004-08-211-2/+3
| | | | Guilty of bad merge: trhodes
* Document recently added features and bump the doc date.trhodes2004-08-211-1/+41
|
* Fix positional parameter reference to ${10}.thomas2004-08-211-4/+4
| | | | | | Fix target location for generation of fstab. PR: bin/70795
* Allow mac_bsdextended(4) to log failed attempts to syslog's AUTHPRIVtrhodes2004-08-211-5/+19
| | | | | | | | facility. This is disabled by default but may be turned on by using the mac_bsdextended_logging sysctl. Reviewed by: re (jhb) Approved by: re (jhb)
* Give the mac_bsdextended(4) policy the ability to match and apply on a firsttrhodes2004-08-211-2/+21
| | | | | | | | | | rule only in place of all rules match. This is similar to how ipfw(8) works. Provide a sysctl, mac_bsdextended_firstmatch_enabled, to enable this feature. Reviewed by: re (jhb) Aprroved by: re (jhb)
* Clarify __FreeBSD_version scheme.obrien2004-08-211-1/+3
| | | | Submitted by: ru
* Hit people over the head so they realize run-time errors of the formobrien2004-08-211-5/+8
| | | | | /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE" does mean they are hitting the GCC 3.4 ABI change issue.
* Further reduce the use of Giant by vm_fault(): Giant is held only whenalc2004-08-211-4/+3
| | | | | | | | manipulating a vnode, e.g., calling vput(). This reduces contention for Giant during many copy-on-write faults, resulting in some additional speedup on SMPs. Note: debug_mpsafevm must be enabled for this optimization to take effect.
* Properly free the temporary sf_buf in uiomove_fromphys() if a copyin oralc2004-08-212-2/+7
| | | | | | copyout fails. Obtained from: DragonFlyBSD
* Fix PCI link irq programming on resume. A logic bug prevented a devicenjl2004-08-211-1/+1
| | | | | | | match, inverting which links actually got resumed. Submitted by: Hiroyuki Aizu <eyes_at_navi.org> MFC after: 3 days
* Add regression test for the new "round-robin reading" feature.pjd2004-08-211-0/+36
|
* Implement new reading algorithm, which will use parity component for readingpjd2004-08-215-111/+173
| | | | | | | | | | | | | | | | | | | | | | | | as well, even if device is in complete state. I observe 40% of speed-up with this option for random read operations, but slowdown for sequential reads. Basically, without this option reading from a RAID3 device built from 5 components (c0-c4) looks like this: Request no. Used components 1 c0+c1+c2+c3 2 c0+c1+c2+c3 3 c0+c1+c2+c3 With the new feature: Request no. Used components 1 c0+c1+c2+c3 2 (c1^c2^c3^c4)+c1+c2+c3 3 c0+(c0^c2^c3^c4)+c2+c3 4 c0+c1+(c0^c1^c3^c4)+c3 5 c0+c1+c2+(c0^c1^c2^c4) 6 c0+c1+c2+c3 [...]
* Fix where my automated script blew the SCM ID format conversion.obrien2004-08-213-9/+9
|
* When a prison is given the ability to create raw sockets (when thecsjp2004-08-213-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | security.jail.allow_raw_sockets sysctl MIB is set to 1) where privileged access to jails is given out, it is possible for prison root to manipulate various network parameters which effect the host environment. This commit plugs a number of security holes associated with the use of raw sockets and prisons. This commit makes the following changes: - Add a comment to rtioctl warning developers that if they add any ioctl commands, they should use super-user checks where necessary, as it is possible for PRISON root to make it this far in execution. - Add super-user checks for the execution of the SIOCGETVIFCNT and SIOCGETSGCNT IP multicast ioctl commands. - Add a super-user check to rip_ctloutput(). If the calling cred is PRISON root, make sure the socket option name is IP_HDRINCL, otherwise deny the request. Although this patch corrects a number of security problems associated with raw sockets and prisons, the warning in jail(8) should still apply, and by default we should keep the default value of security.jail.allow_raw_sockets MIB to 0 (or disabled) until we are certain that we have tracked down all the problems. Looking forward, we will probably want to eliminate the references to curthread. This may be a MFC candidate for RELENG_5. Reviewed by: rwatson Approved by: bmilekic (mentor)
* When notifying protocol components of an event on an in6pcb, use therwatson2004-08-211-3/+5
| | | | | | | | | | result of the notify() function to decide if we need to unlock the in6pcb or not, rather than always unlocking. Otherwise, we may unlock and already unlocked in6pcb. Reported by: kuriyama, Gordon Bergling <gbergling at 0xfce3.net> Tested by: kuriyama, Gordon Bergling <gbergling at 0xfce3.net> Discussed with: mdodd
* When prepending space onto outgoing UDP datagram payloads to hold therwatson2004-08-211-4/+7
| | | | | | | | | UDP/IP header, make sure that space is also allocated for the link layer header. If an mbuf must be allocated to hold the UDP/IP header (very likely), then this will avoid an additional mbuf allocation at the link layer. This trick is also used by TCP and other protocols to avoid extra calls to the mbuf allocator in the ethernet (and related) output routines.
* Add &release.type.current; to unbreak the build.hrs2004-08-211-0/+21
|
* mdoc(7) janitor:simon2004-08-212-2/+4
| | | | | | - Fix hard sentence breaks. MFC after: 3 days
* Add &release.type.current; to unbreak the build.hrs2004-08-211-0/+22
|
* Pull debug symbols in for statically linked binary.davidxu2004-08-212-0/+8
| | | | Reviewed by: desichen
* Bump version numbers for 6.0-CURRENT and fix some sentences.hrs2004-08-213-24/+27
|
* Attempt to make the probe for hardware more specific.phk2004-08-211-3/+22
|
* Back out the call to _init_tls() - something is broken there and itdfr2004-08-211-2/+0
| | | | prevents all static binaries from running.
* The UTF2 encoding and the INVALID keyword are now obsolete.tjr2004-08-211-3/+3
|
* Re-word warning about the UTF2 encoding, taking care to use the wordtjr2004-08-211-3/+3
| | | | "obsolete" instead of "deprecated".
* Bump document date for previous.tjr2004-08-212-2/+2
|
* Re-word warning about the rune interface, taking care to use the wordtjr2004-08-212-12/+10
| | | | "obsolete" instead of "deprecated".
* Change "deprecated" in link-time warnings about various rune functionstjr2004-08-214-8/+8
| | | | to "obsolete".
* Re-word compatibility section, taking care to use the word "obsolete" totjr2004-08-2114-54/+64
| | | | | describe the 4.4BSD extension of accepting characters (runes) outside of the range of unsigned char.
* Avoid accidental use of ANSI C trigraphs.maxim2004-08-211-1/+2
| | | | | Spotted by: Pawel Worach Obtained from: NetBSD (rev. 1.11, 1.13)
* Let GCC know that ___runetype(), ___tolower() and ___toupper() are puretjr2004-08-211-3/+3
| | | | | | | functions, allowing it to generate better code for the <ctype.h> and <wctype.h> functions. For example, it can now keep _CurrentRuneLocale in a register across calls to these functions, and can delete calls to ___runetype() if the result is already known or not used.
* Fix aperture size detection on some ALi chipsets by only using the lowest 4 bitsanholt2004-08-212-8/+8
| | | | | | | | | to check aperture size, avoiding hangs. Maintain the rest of the bits when setting/unsetting ATTBASE. This essentially matches Linux's AGP driver as well. PR: kern/70037 Submitted by: Mark Tinguely <tinguely at casselton dot net> Obtained from: NetBSD
* Apply some stylistic changes based off of kern/70037 (content changes toanholt2004-08-212-20/+20
| | | | follow).
* Enter the long awaited start of FreeBSD 6.0!obrien2004-08-211-1/+1
|
* Add some details about our wonderful system.obrien2004-08-211-1/+17
|
* Document when this function came into FreeBSD.obrien2004-08-211-1/+3
|
* Don't bother calling the module event handlers from module_shutdown()truckman2004-08-201-0/+3
| | | | | | | | | | | | | | in the shutdown_final state if the RB_NOSYNC flag is set. The specific motivation in this case is that a system panic in an interrupt context results in a call to module_shutdown(), which calls g_modevent(), which calls g_malloc(..., M_WAITOK), which results in a second panic. While g_modevent() could be fixed to not call malloc() for MOD_SHUTDOWN events (which it doesn't handle in any case), it is probably also a good idea to entirely skip the execution of the module shutdown handlers after a panic. This may be a MFC candidate for RELENG_5.
OpenPOWER on IntegriCloud