summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Be consistent about functions being static.phk2002-10-167-12/+12
| | | | Spotted by: FlexeLint
* Be consistent about funtions being static.phk2002-10-161-11/+11
| | | | Spotted by: FlexeLint
* Put an XXX: comment here to point out a couple of free() issues onphk2002-10-161-0/+4
| | | | | | pnp_read_bytes(). Spotted by: FlexeLint
* No need to declare M_ISADEV here.phk2002-10-161-2/+0
| | | | Spotted by: FlexeLint.
* Be consistent about funtions being static.phk2002-10-168-25/+39
| | | | Spotte by: FlexeLint.
* Be consistent about functions being static.phk2002-10-162-32/+32
| | | | | | Fix misindentation. Spotted by: DARPA & NAI Labs.
* Be consistent about functions being static.phk2002-10-161-1/+1
| | | | Spotted by: FlexeLint.
* Be consistent about functions being static.phk2002-10-167-31/+31
| | | | | | Properly put macro args in (). Spotted by: FlexeLint.
* Properly put macro args in ().phk2002-10-161-1/+1
| | | | Spotted by: FlexeLint.
* Be consistent about functions being static.phk2002-10-168-29/+33
| | | | Spotted by: FlexeLint.
* Get rid of checking for ip sec history. It is true that packets are notguido2002-10-161-5/+0
| | | | | | | | | | | | | | | | | | | | | supposed to be checked by the firewall rules twice. However, because the various ipsec handlers never call ip_input(), this never happens anyway. This fixes the situation where a gif tunnel is encrypted with IPsec. In such a case, after IPsec processing, the unencrypted contents from the GIF tunnel are fed back to the ipintrq and subsequently handeld by ip_input(). Yet, since there still is IPSec history attached, the packets coming out from the gif device are never fed into the filtering code. This fix was sent to Itojun, and he pointed towartds http://www.netbsd.org/Documentation/network/ipsec/#ipf-interaction. This patch actually implements what is stated there (specifically: Packet came from tunnel devices (gif(4) and ipip(4)) will still go through ipf(4). You may need to identify these packets by using interface name directive in ipf.conf(5). Reviewed by: rwatson MFC after: 3 weeks
* FIx misindentation.phk2002-10-162-22/+25
| | | | Spotted by: FlexeLint.
* Be consistent about functions being static.phk2002-10-1610-10/+10
| | | | Spotted by: FlexeLint.
* Be consistent about functions being static.phk2002-10-1611-26/+26
| | | | Spotted by: FlexeLint.
* Fix misindentation.phk2002-10-161-2/+2
| | | | Spotted by: FlexeLint
* Rename struct softc to struct mn_softc.phk2002-10-161-27/+31
|
* Fix comments and one resulting code confusion about the type of thephk2002-10-169-9/+10
| | | | | | "command" argument to VOP_IOCTL. Spotted by: FlexeLint.
* Be consistent about functions being static.phk2002-10-162-2/+2
| | | | Spotted by: FlexeLint
* A better solution to avoiding variable sized structs in DEVFS.phk2002-10-162-3/+5
|
* #include "opt_devfs.h" to protect against variable sized structures.phk2002-10-161-0/+2
| | | | Spotted by: FlexeLint
* Never allow memory mapped I/O in PCI-X mode on controllers thatgibbs2002-10-161-2/+4
| | | | | do not support that configuration. This should fix problems with embedded 7902 controllers running in PCI-X mode.
* correct PCB locking in broadcast/multicast case that was exposed by changesam2002-10-161-1/+1
| | | | | | to use udp_append Reviewed by: hsu
* Tie new "Fast IPsec" code into the build. This involves the usualsam2002-10-1625-96/+605
| | | | | | | | | | | | configuration stuff as well as conditional code in the IPv4 and IPv6 areas. Everything is conditional on FAST_IPSEC which is mutually exclusive with IPSEC (KAME IPsec implmentation). As noted previously, don't use FAST_IPSEC with INET6 at the moment. Reviewed by: KAME, rwatson Approved by: silence Supported by: Vernier Networks
* add definitions for RIPEMD-160 HMAC and Skipjack encryption algorithms,sam2002-10-161-0/+2
| | | | for use by "Fast IPsec"
* "Fast IPsec": this is an experimental IPsec implementation that is derivedsam2002-10-1626-0/+17530
| | | | | | | | | | | | | | | | | | | | | | | from the KAME IPsec implementation, but with heavy borrowing and influence of openbsd. A key feature of this implementation is that it uses the kernel crypto framework to do all crypto work so when h/w crypto support is present IPsec operation is automatically accelerated. Otherwise the protocol implementations are rather differet while the SADB and policy management code is very similar to KAME (for the moment). Note that this implementation is enabled with a FAST_IPSEC option. With this you get all protocols; i.e. there is no FAST_IPSEC_ESP option. FAST_IPSEC and IPSEC are mutually exclusive; you cannot build both into a single system. This software is well tested with IPv4 but should be considered very experimental (i.e. do not deploy in production environments). This software does NOT currently support IPv6. In fact do not configure FAST_IPSEC and INET6 in the same system. Obtained from: KAME + openbsd Supported by: Vernier Networks
* Replace aux mbufs with packet tags:sam2002-10-1643-474/+370
| | | | | | | | | | | | | | | | | | | o instead of a list of mbufs use a list of m_tag structures a la openbsd o for netgraph et. al. extend the stock openbsd m_tag to include a 32-bit ABI/module number cookie o for openbsd compatibility define a well-known cookie MTAG_ABI_COMPAT and use this in defining openbsd-compatible m_tag_find and m_tag_get routines o rewrite KAME use of aux mbufs in terms of packet tags o eliminate the most heavily used aux mbufs by adding an additional struct inpcb parameter to ip_output and ip6_output to allow the IPsec code to locate the security policy to apply to outbound packets o bump __FreeBSD_version so code can be conditionalized o fixup ipfilter's call to ip_output based on __FreeBSD_version Reviewed by: julian, luigi (silent), -arch, -net, darren Approved by: julian, silence from everyone else Obtained from: openbsd (mostly) MFC after: 1 month
* Change locking so that all snapshots on a particular filesystem sharemckusick2002-10-161-42/+91
| | | | | | | | | | | | | | | a common lock. This change avoids a deadlock between snapshots when separate requests cause them to deadlock checking each other for a need to copy blocks that are close enough together that they fall into the same indirect block. Although I had anticipated a slowdown from contention for the single lock, my filesystem benchmarks show no measurable change in throughput on a uniprocessor system with three active snapshots. I conjecture that this result is because every copy-on-write fault must check all the active snapshots, so the process was inherently serial already. This change removes the last of the deadlocks of which I am aware in snapshots. Sponsored by: DARPA & NAI Labs.
* missed additional callout that can run w/o Giant lockedsam2002-10-151-1/+2
|
* Include "opt_kbd.h" since certain structures size depend on the valuephk2002-10-152-0/+4
| | | | | | | | | | | | | | of KBDIO_DEBUG which may be defined in the kernel config (as it is in NOTES). This kind of bug is a _really_ horribly thing as we end up with one bit of code thinking a particular structure is 136 bytes and another that it is only 112 bytes. Ideally all places would remember to #include the right "opt_foo.h" file, but I think in practice file containing the variable sized struct should #include it explicitly as a precaution. Detected by: FlexeLint
* Return an error if the drive reports heads/sectors that do not make sense.njl2002-10-151-0/+8
| | | | | | This fixes a divide by zero in fdisk(8) Reviewed by: phk
* Push most UFS ACL behavior behind a check for MNT_ACLS, permitting ACLsrwatson2002-10-152-101/+129
| | | | | | | | | | | | to be administratively disabled as needed on UFS/UFS2 file systems. This also has the effect of preventing the slightly more expensive ACL code from running on non-ACL file systems, avoiding storage allocation for ACLs that may be read from disk. MNT_ACLS may be set at mount-time using mount -o acls, or implicitly by setting the FS_ACLS flag using tunefs. On UFS1, you may also have to configure ACL store. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Bump __FreeBSD_version for the Binutils 2.13 upgrade, which includes theobrien2002-10-151-1/+1
| | | | new FreeBSD emulation, vec, and output format.
* Correct the definitions of SADB_* to be compatible withume2002-10-151-15/+15
| | | | | | RFC2407/IANA assignment. This change breaks binary compatibility. So, you need to recompile IPsec related applications.
* Don't show the command line when doing "make lint".phk2002-10-151-1/+1
|
* Be consistent about marking functions static.phk2002-10-157-30/+31
| | | | Found by: FlexeLint.
* If the FS_MULTILABEL flag is set in a UFS or UFS2 superblock,rwatson2002-10-151-0/+17
| | | | | | | | | | | | | | automatically set MNT_MULTILABEL in the mount flags. If FS_ACLS is set in a UFS or UFS2 superblock, automatically set MNT_ACLS in the mount flags. If either of these flags is set, but the appropriate kernel option to support the features associated with the flag isn't available, then print a warning at mount-time. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Plug a memory-leak.phk2002-10-151-0/+1
| | | | "I think you're right" by: jake
* Use ; not , as statement separator in PDEBUG() macro.phk2002-10-151-5/+4
| | | | | | | | | | | Ignoring a NULL dev in device_set_ivars() sounds wrong, KASSERT it to non-NULL instead. Do the same for device_get_ivars() for reasons of symmetry, though it probably would have yielded a panic anyway, this gives more precise diagnostics. Absentmindedly nodded OK to by: jhb
* Plug an infrequent (I think) memory leak.phk2002-10-151-1/+3
| | | | Spotted by: FlexeLint
* Constification ? Yes, out that door, row on the left, one patch each.phk2002-10-152-10/+10
| | | | Sponsored by: DARPA & NAI Labs
* Argh. Put back setting of P_ADVLOCK for the F_WRLCK case that wasjhb2002-10-151-0/+3
| | | | | | | accidentally lost in the previous revision. Submitted by: bde Pointy hat to: jhb
* Fix kernel module loading on ia64. Cross-module function callsmarcel2002-10-154-4/+36
| | | | | | | | | | | | were improperly relocated due to faulty logic in lookup_fdesc() in elf_machdep.c. The symbol index (symidx) was bogusly used for load modules other than the one the relocation applied to. This resulted in bogus bindings and consequently runtime failures. The fix is to use the symbol index only for the module being relocated and to use the symbol name for look-ups in the modules in the dependent list. As such, we need a function to return the symbol name given the linker file and symbol index.
* Enable mpt && ISP_TARGET_MODE in isp (for Lint purposes)mjacob2002-10-151-1/+4
|
* Fix previous commit: Don't cast integral types to pointers tomarcel2002-10-152-4/+4
| | | | | | print them with %p. Cast to unsigned long and print with %#lx. Discussed with: bde
* Restore pointer that was removed in 1.128. This wasn't a merge-o.peter2002-10-151-0/+4
|
* Move details of key_t to <sys/_types.h>, so that it can be typedef'dmike2002-10-152-1/+6
| | | | in more than just <sys/types.h>.
* - Add a new global mutex 'ppeers_lock' to protect the p_peers list ofjhb2002-10-154-45/+61
| | | | | | | | | | | | | | | | | | | processes forked with RFTHREAD. - Use a goto to a label for common code when exiting from fork1() in case of an error. - Move the RFTHREAD linkage setup code later in fork since the ppeers_lock cannot be locked while holding a proc lock. Handle the race of a task leader exiting and killing its peers while a peer is forking a new child. In that case, go ahead and let the peer process proceed normally as the parent is about to kill it. However, the task leader may have already gone to sleep to wait for the peers to die, so the new child process may not receive a SIGKILL from the task leader. Rather than try to destruct the new child process, just go ahead and send it a SIGKILL directly and add it to the p_peers list. This ensures that the task leader will wait until both the peer process doing the fork() and the new child process have received their KILL signals and exited. Discussed with: truckman (earlier versions)
* Remove the leaderp variable and just access p_leader directly. Thejhb2002-10-151-12/+3
| | | | | p_leader field is not protected by the proc lock but is only set during fork1() by the parent process and never changes.
* - Use __BUS_ACCESSOR() to define the ISA ivar accessor functions instead ofjhb2002-10-152-22/+10
| | | | | | | | homerolling our own version. - Rename the enum for memsize from ISA_IVAR_MSIZE to ISA_IVAR_MEMSIZE since using 'MSIZE' in the macro invocation of ISA_ACCESSOR() conflicts with the 'MSIZE' kernel option. The accessor function is still isa_get_msize().
* The a.out md_coredump stuff isn't referenced anywhere anymore, andpeter2002-10-157-47/+1
| | | | hasn't been filled in for ages.. Nuked.
OpenPOWER on IntegriCloud