summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Expand contractions.joel2006-02-019-13/+13
|
* 1) Fix link state detection for cards operating in TBI mode (fiber ones)oleg2006-02-012-25/+31
| | | | | | | | 2) add missing bus_dmamap_sync() call in bge_intr() Tested by: Husnu Demir <hdemir AT metu DOT edu DOT tr> Approved by: glebius (mentor) MFC after: 3 days
* Move the IPSEC related code blocks to their own file to unclutterandre2006-02-015-445/+655
| | | | | | | | | | | | | | and signifincantly improve the readability of ip_input() and ip_output() again. The resulting IPSEC hooks in ip_input() and ip_output() may be used later on for making IPSEC loadable. This move is mostly mechanical and should preserve current IPSEC behaviour as-is. Nothing shall prevent improvements in the way IPSEC interacts with the IPv4 stack. Discussed with: bz, gnn, rwatson; (earlier version)
* Record the change in vnone_create_vobject() argument size,yar2006-02-011-0/+4
| | | | | which broke kernel ABI to filesystem modules on i386, where sizeof(size_t) != sizeof(off_t).
* Use off_t for file size passed to vnode_create_vobject().yar2006-02-012-2/+2
| | | | | | | | | The former type, size_t, was causing truncation to 32 bits on i386, which immediately led to undersizing of VM objects backed by files >4GB. In particular, sendfile(2) was broken for such files. PR: kern/92243 MFC after: 5 days
* Remove trailing spaces.pjd2006-02-0112-28/+28
|
* Remove trailing spaces.pjd2006-02-0128-67/+67
|
* Remove unsupported hardware.nyan2006-02-011-2/+0
| | | | X-MFC after: soon
* Setting IFF_ALLMULTI on a running interface didn't call bge_setmulti()ru2006-02-011-1/+4
| | | | | | as intended, resulting in a non-working multicast routing. Fix it. MFC after: 3 days
* - Install a temporary bandaid in vm_object_reference() that will stopjeff2006-02-011-5/+5
| | | | mtx_assert()s from triggering until I find a real long-term solution.
* - Solve a problem where a vput could be called on an outgoing directoryjeff2006-02-011-5/+13
| | | | | | | | | without Giant held. Do this by tracking the vfslocked state for the directory seperate from the child. This is only important in the case where we cross a mountpoint. Sponsored by: Isilon Systems, Inc. MFC After: 3 days
* - chroot and chdir need to lock giant as appropriate for the outgoing vpjeff2006-02-012-0/+10
| | | | | | | as well as the new vp. Sponsored by: Isilon Systems, Inc. MFC After: 3 days
* Brain-o (use standard int types now).ru2006-02-011-2/+2
|
* Fix another compile problem. If I find any more, this file is going in thescottl2006-02-011-1/+1
| | | | Attic until it is properly fixed.
* - Solve a race where we could lose a call to VOP_INACTIVE. If vget() waitingjeff2006-02-011-12/+30
| | | | | | | | | | | | | on a lock held the last usecount ref on a vnode and the lock failed we would not call INACTIVE. Solve this by only holding a holdcnt to prevent the vnode from disappearing while we wait on vn_lock. Other callers may now VOP_INACTIVE while we are waiting on the lock, however this race is acceptable, while losing INACTIVE is not. Discussed with: kan, pjd Tested by: kkenn Sponsored by: Isilon Systems, Inc. MFC After: 1 week
* - Reorder calls to vrele() after calls to vput() when the vrele is ajeff2006-02-018-88/+81
| | | | | | | | | | | | directory. vrele() may lock the passed vnode, which in these cases would give an invalid lock order of child -> parent. These situations are deadlock prone although do not typically deadlock because the vrele is typically not releasing the last reference to the vnode. Users of vrele must consider it as a call to vn_lock() and order it appropriately. MFC After: 1 week Sponsored by: Isilon Systems, Inc. Tested by: kkenn
* Attach ce(4) to the build.rik2006-01-314-0/+10
| | | | MFC after: 3 days
* Remove duplicate model entry.rik2006-01-311-4/+0
|
* - Sync the list of supported chips with pcn_probe() as of sys/pci/if_pcn.cmarius2006-01-311-7/+3
| | | | | | | | | | rev. 1.77, i.e. remove Am53C974/Am79C970/Am79C974 PCnet-PCI and Am79C970A PCnet-PCI II. - Change the entry of the PCnet-Home in the list of supported chips to match the other ones, i.e. s,PCnet/Home HomePNA,Am79C978 PCnet-Home,. - s,familly,family MFC after: 1 day
* Add RWLOCK_NOINLINE.jhb2006-01-311-1/+8
|
* Add a reference to le(4) as the SBus-based Ultra 1 have on-board LANCE.marius2006-01-311-1/+2
|
* Add le(4) to the list of devices supporting VLAN-sized frames natively.marius2006-01-311-1/+5
|
* Add a man page for le(4), based on the NetBSD one.marius2006-01-312-0/+371
|
* Fix multicast routing on 64-bit platforms.ru2006-01-311-2/+2
| | | | | Tested on: amd64 MFC after: 3 days
* Hook up le(4) to the build. For now it's only added to the sparc64 GENERICmarius2006-01-316-2/+24
| | | | | | | in order to support the on-board LANCE in Ultra 1 and to the MI NOTES as it should work just fine with the AMD PCnet family of chips on all archs but is not yet meant to replace lnc(4). If a kernel includes all of le(4), lnc(4) and pcn(4) precedence is given to lnc(4)/pcn(4) for now.
* Allow root to open prison pts devices too.csjp2006-01-311-1/+1
| | | | Pointed out by: rwatson
* Clarify time frame of jkh quote.grog2006-01-311-1/+1
|
* Add wisdom from jkh.grog2006-01-311-0/+16
|
* Now that the bridge also processes Ethernet frames as itself, two arp repliesthompsa2006-01-311-2/+4
| | | | | | | | | will be sent if there is an address on the bridge. Exclude the bridge from the special arp handling. This has been tested with all combinations of addresses on the bridge and members. Pointed out by: Michal Mertl
* Fix two bugs with the bridgethompsa2006-01-311-3/+17
| | | | | | | | | | | | - code expects memcmp() to return a signed value, our memcmp() returns 0 if args are equal and > 0 if not. - It's possible to hijack interface for static entry. If bridge recieves packet from interface marked as learning it will replace the bridge_rtnode entry for the source address even if such entry marked as static. Submitted by: Gleb Kurtsov <k-gleb yandex.ru> MFC after: 3 days
* some updates to the manpage.luigi2006-01-311-79/+39
| | | | | | remove references to mdconfig/vnconfig, and remove some of the references to floppies since they are rarely used at all now.
* tweaks to let this configuratio build and run under, e.g., qemu:luigi2006-01-312-2/+4
| | | | | | | | | | - add -lgeom - use bsdlabel instead of disklabel - increase image size to 2.88M (plenty of free space left) note, this is not really a bridge because the old-style bridging code is not in 7.0 anymore, so the kernel config file should be changed.
* Retroactively add a note about the device names in /dev for si(4) changing.jhb2006-01-311-0/+4
|
* unbreak the build script.luigi2006-01-311-169/+103
| | | | | Instead of using vnconfig/mdconfig it relies on the makefs port to build the image (UFS1) without need for root permissions.
* This commit was generated by cvs2svn to compensate for changes in r155131,rwatson2006-01-3172-0/+15884
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Initial vendor import of the TrustedBSD OpenBSM distribution, versionrwatson2006-01-3172-0/+15884
| | | | | | | | | | | | | | | | | | | | | | | 1.0 alpha 1, an implementation of the documented Sun Basic Security Module (BSM) Audit API and file format, as well as local extensions to support the Mac OS X and FreeBSD operating systems. Also included are command line tools for audit trail reduction and conversion to text, as well as documentation of the commands, file format, and APIs. This distribution is the foundation for the TrustedBSD Audit implementation, and is a pre-release. This is the first in a series of commits to introduce support for Common Criteria CAPP security event audit support. This software has been made possible through the generous contributions of Apple Computer, Inc., SPARTA, Inc., as well as members of the TrustedBSD Project, including Wayne Salamon <wsalamon> and Tom Rhodes <trhodes>. The original OpenBSM implementation was created by McAfee Research under contract to Apple Computer, Inc., as part of their CC CAPP security evaluation. Many thanks to: wsalamon, trhodes Obtained from: TrustedBSD Project
* Document the daily_status_ata_raid_enable and daily_status_gmirror_enablebrueffer2006-01-311-1/+19
| | | | variables.
* ADDON is registered as 0x0d7d, not PNY. Don't confuse the two as weimp2006-01-312-14/+24
| | | | | | | try to use the registrant for numbers in this file, not the OEM that put their label on it. Use PNY's real number 0x154b. Add another PNY atachmate with quirks from a PR filed a while ago, but that I can't seem to find now...
* Change #if defined(DIAGNOSTIC) to KASSERT.alc2006-01-311-4/+3
|
* The newly added le(4) driver is altq capable.brueffer2006-01-311-1/+2
|
* Fix a typo and match the copyright on rwlock.h.jhb2006-01-311-3/+7
|
* Xref redzone(9)brueffer2006-01-311-2/+3
|
* Allow root in the host environment to open ptys within jailed environments.csjp2006-01-311-1/+1
| | | | | | | | | | | | | | This logic change was introduced in revision 1.74: Correct an oversight in jail() that allowed processes in jail to access ptys in ways that might be unethical, especially towards processes not in jail, or in other jails. It should be fine to allow root in the host environment to do this. This allows for more effective monitoring of prisons from the host environment. Discussed with: rwatson MFC after: 1 week
* sys/linker.h needs sys/systm.h as a requirement.mlaier2006-01-311-0/+1
| | | | Submitted by: gallatin
* Set IFF_BROADCAST and IFF_MULTICAST on vlan interfaces from theyar2006-01-311-2/+5
| | | | | | | | | | | | | | | | | | beginning and simply refuse to attach to a parent without either flag. Our network stack cannot handle well IFF_BROADCAST or IFF_MULTICAST on an interface changing on the fly. E.g., IP will or won't assign a broadcast address to an interface and join the all-hosts multicast group on it depending on its IFF_BROADCAST and IFF_MULTICAST settings. Should the flags alter later, IP will miss the change and keep using bogus settings. This can lead to evil things like supplying an invalid broadcast address or trying to leave a multicast group that hasn't been joined. So just avoid touching the flags since an interface was created. This has no practical purpose. Discussed with: -net, glebius, oleg MFC after: 1 week
* Remove unused argument.pjd2006-01-311-3/+2
| | | | MFC after: 3 days
* This commit was generated by cvs2svn to compensate for changes in r155094,harti2006-01-311-1/+3
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Vendor patch: prevent a core dump when the trace option is not followedharti2006-01-311-1/+3
| | | | | | | | | | | | by an option value. Submitted by: Shteryana Shopova <shteryana@yahoo.com>
* | Add le(4), a driver for AMD Am7900 LANCE and Am79C9xx PCnet NICs portedmarius2006-01-3111-0/+4374
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from NetBSD. This driver actually can replace lnc(4). Advantages over lnc(4) are: - Cleaner and more flexible regarding MD needs. - Endian-clean and MPSAFE. - Supports ALTQ, VLAN_MTU, ifmedia. - Uses 32bit DMA for the PCI variants. This commit includes front-ends for the dma(4) pseudo-bus found on SBus- based sparc64 machines (thus supports the on-board LANCE in Sun Ultra 1) and PCI. In order to actually replace lnc(4), the front-ends for ISA and the PC98 CBUS would have to be added but for which I don't have hardware to test. Reviewed and some improvements by: yongari Tested on: i386, sparc64
* | make sure that the start and end preloaded MFS markers areluigi2006-01-311-4/+14
| | | | | | | | | | in contiguous strings, and that the compiler does not optimize them away because it thinks they are unused.
OpenPOWER on IntegriCloud