summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Don't set PACKAGE_BUILDING while installing packages.flz2008-07-171-1/+0
| | | | | | Submitted by: erwin Discussed on: http://lists.freebsd.org/pipermail/freebsd-ports/2008-June/049074.html MFC after: 1 week
* Before updating the password database, the pw(8) utility first performs ajhb2008-07-171-1/+2
| | | | | | | | sanity check by invoking "pwd_mkdb -C". However, if this failed it silently returned success. Fix this so it fails the update operation instead. MFC after: 1 week
* Add the shutdown KEYWORD to those scripts that start persistent servicesdougb2008-07-1634-19/+34
| | | | | | | | | | | to allow them to do a "clean" shutdown. I purposely avoided making changes to network-related stuff since the system shutting down is pretty conclusive, and there may be complicated dependencies on the network that I would rather not try to unravel. I also skipped kerberos-related stuff for the reasons above, and because I have no way to test it.
* As previously discussed, add the svn:executable property to all scriptsdougb2008-07-1692-0/+0
|
* Move the TCSA* definitions out of _KERNEL. They are processed in libc.ed2008-07-161-10/+10
| | | | | | | | The tcsetattr() routine already converts the TCSA* arguments to their respective TIOCSETA* ioctl's in the C library. There is no need to have these definitions inside the kernel. Approved by: philip (mentor, implicit)
* Sort the ioctl's in <sys/ttycom.h> by number.ed2008-07-161-48/+48
| | | | | | | | I think one of the reasons why we have so many conflicts in the TTY ioctl category, is because the ioctl's aren't ordered logically. This commit only sorts them by number. The comments may still be inaccurate. Approved by: philip (mentor)
* Remove OTTYDISC, NETLDISC and NTTYDISC definitions.ed2008-07-163-17/+0
| | | | | | | | | | | | | | | | When I ported most applications away from <sgtty.h>, I noticed none of them were actually using these definitions. I kept them in place, because I didn't want to touch tools like pstat(8) and stty(1). In preparation for the MPSAFE TTY layer, remove these definitions. This doesn't have any impact with respect to binary compatibility (see tty_conf.c). We couldn now add an #error to <sys/ioctl_compat.h> when included outside the kernel. Unfortunately, kdump's mkioctls includes this file unconditionally. Approved by: philip (mentor)
* Fix error in comment.rwatson2008-07-161-3/+3
| | | | MFC after: 3 weeks
* Fix a multicast handling regression on VT6105M introduced inyongari2008-07-162-25/+60
| | | | | | | | | | | | | | | | | | | | | | | vr(4) overhauling(r177050). It seems that filtering multicast addresses with multicast CAM entries require accessing 'CAM enable bit' for each CAM entry. Subsequent accessing multicast CAM control register without toggling the 'CAM enable bit' seem to no effects. In order to fix that separate CAM setup from CAM mask configuration and CAM entry modification. While I'm here add VLAN CAM filtering feature which will be enabled in future(FreeBSD now can receive VLAN id insertion/removal event from vlan(4) on the fly). For VT6105M hardware, explicitly disable VLAN hardware tag insertion/stripping and enable VLAN CAM filtering for VLAN id 0. This shall make non-VLAN frames set VR_RXSTAT_VIDHIT bit in Rx status word. Added multicast/VLAN CAM address definition to header file. PR: kern/125010, kern/125024 MFC after: 1 week
* Fix VR_RXSTAT_RX_OK bit definition which lasted for more than 9yongari2008-07-162-3/+4
| | | | | | | | | | | | | years. All datasheet I have indicates the bit 15 is the VR_RXSTAT_RX_OK. The bit 14 is reserved for all Rhine family except VT6105M. VT6105M uses that bit to indicate a VLAN frame with matching CAM VLAN id. Use the VR_RXSTAT_RX_OK instead of VR_RXSTAT_RXERR when vr(4) checks the validity of received frame. This should fix occasional dropping frames on VT6105M. Tested by: Goran Lowkrantz ( goran.lowkrantz at ismobile dot com ) MFC after: 1 week
* Invoke err() with a format string rather than directly with a passedrwatson2008-07-151-1/+1
| | | | | | | | command line argument. Submitted by: Alfredo Ortega <alfredo at coresecurity dot com> Thanks to: Core Security Technologies MFC after: 3 days
* Merge last of a series of rwlock conversion changes to UDP, whichrwatson2008-07-152-34/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | completes the move to a fully parallel UDP transmit path by using global read, rather than write, locking of inpcbinfo in further semi-connected cases: - Add macros to allow try-locking of inpcb and inpcbinfo. - Always acquire an incpcb read lock in udp_output(), which stablizes the local inpcb address and port bindings in order to determine what further locking is required: - If the inpcb is currently not bound (at all) and are implicitly connecting, we require inpcbinfo and inpcb write locks, so drop the read lock and re-acquire. - If the inpcb is bound for at least one of the port or address, but an explicit source or destination is requested, trylock the inpcbinfo lock, and if that fails, drop the inpcb lock, lock the global lock, and relock the inpcb lock. - Otherwise, no further locking is required (common case). - Update comments. In practice, this means that the vast majority of consumers of UDP sockets will not acquire any exclusive locks at the socket or UDP levels of the network stack. This leads to a marked performance improvement in several important workloads, including BIND, nsd, and memcached over UDP, as well as significant improvements in pps microbenchmarks. The plan is to MFC all of the rwlock changes to RELENG_7 once they have settled for a weeks in the tree. Tested by: ps, kris (older revision), bde MFC after: 3 weeks
* Fix commment in typo.rpaulo2008-07-151-1/+1
| | | | M tcp_output.c
* Update the definition of modspecific structuredanger2008-07-151-3/+3
| | | | PR: docs/125630
* Update bus_dmamem_alloc()'s first call to malloc() such that M_WAITOK isalc2008-07-153-10/+10
| | | | | | specified when appropriate. Reviewed by: scottl
* Add quirk for Dell D630 laptops.delphij2008-07-151-1/+7
| | | | | | | Tested by: Quake Lee <quakelee geekcn org>, Robert Noland <rnoland 2hip net> MFC after: 1 week Approved by: ariff
* Allow injecting big packets via bpf(4) up to min(MTU, 16K-byte).jkim2008-07-141-3/+9
| | | | MFC after: 1 week
* Match the implementation of the inline function from libkern.h.obrien2008-07-142-5/+17
|
* Fix carp(4) panics that can occur during carp interface configuration.eri2008-07-141-0/+8
| | | | | | Approved by: mlaier (mentor) Reported by: Scott Ullrich MFC after: 1 week
* Unmangle an E.W.Dijkstra quote.phk2008-07-141-3/+5
|
* Add event notification at attach/detach so the NICjfv2008-07-141-0/+6
| | | | is able to detect it and do hardware filtering.
* Add an event handler to the vlan driver so the NIC driverjfv2008-07-141-0/+7
| | | | | | becomes aware of it, and gets the VLAN ID. This will allow the easy use of VLAN hardware filtering by adapters that support it.
* Manpage for the et(4) driver.brueffer2008-07-142-0/+182
| | | | Obtained from: DragonFly
* Fill in the string portion of the bluetooth stack version sysctl.trhodes2008-07-141-1/+1
| | | | Approved by: emax
* - Enhance volume handlinggahr2008-07-142-10/+38
| | | | | | PR: 125054 Submitted by: gahr Approved by: cperciva
* Change the character prefixed to the svn version to "r" since that seemsdougb2008-07-131-1/+1
| | | | to be how they are commonly referred to.
* Handle a race between pmap_kextract() and pmap_promote_pde(). This racealc2008-07-131-5/+13
| | | | | | | caused ZFS to crash when restoring a snapshot with superpage promotion enabled. Reported by: kris
* Add an obsolete header after pecoff removal.antoine2008-07-131-0/+4
| | | | Approved by: rwatson (mentor)
* Staticize M_STACK.antoine2008-07-131-1/+1
| | | | | Approved by: rwatson (mentor) MFC after: 1 month
* The libc acl_valid(3) function validates the contents of a POSIX.1e ACL.rwatson2008-07-131-8/+2
| | | | | | | | | | This change removes the requirement that an ACL contain no ACL_USER entries with a uid the same as those of a file, or ACL_GROUP entries with a gid the same as those of a file. This requirement is not in the specification, and not enforced by the kernel's ACL implementation. Reported by: Iustin Pop <iusty at k1024 dot org> MFC after: 1 week
* More explicitly mention that we support the 2920C with the ahc driver.remko2008-07-131-2/+2
| | | | | | PR: 125535 Submitted by: Bob Bishop <rb at gid dot co dot uk> MFC after: 3 days
* Update the ktr_header structure, which changed over time.remko2008-07-131-4/+4
| | | | | | PR: 125546 Submitted by: Mateusz Guzik <mjguzik at gmail dot com> MFC after: 3 days
* Make uart(4) the default serial port driver on i386 and amd64.ed2008-07-137-40/+49
| | | | | | | | | | | The uart(4) driver has the advantage of supporting a wider variety of hardware on a greater amount of platforms. This driver has already been the standard on platforms such as ia64, powerpc and sparc64. I've decided not to change anything on pc98. I'd rather let people from the pc98 team look at this. Approved by: philip (mentor), marcel
* fix multicast hash register definitionticso2008-07-121-2/+2
|
* Refine the changes made in SVN rev 180430. Specifically, instantiate a newalc2008-07-121-16/+26
| | | | | page table page only if the 2MB page mapping has been used. Also, refactor some assertions.
* In nmount(), if we see "update" in the mount options,rodrigc2008-07-121-4/+5
| | | | | | | | | | | | | | | | | | | set MNT_UPDATE in fsflags, and delete the "update" option from the global mount options. MNT_UPDATE is a command, and not a property of a mount that should persist after the command is executed. We need to do similar things for MNT_FORCE and MNT_RELOAD. All mount flags are prefixed by MNT_..... it would be nice if flags which were commands were named differently from flags which are persistent properties of a mount. This was not such a big deal in the pre-nmount() days, but with nmount() it is more important. Requested by: yar MFC after: 2 weeks
* In order to apply pmap_demote_pde() to a page directory entry (PDE) from thealc2008-07-121-2/+3
| | | | | | direct map, the PDE must have PG_M and PG_A preset. Noticed by: Magesh Dhasayyan
* Strongly discourage the use of the query-source option, and explain why.dougb2008-07-121-7/+13
| | | | | | | Give a better example if a user absolutely must use this option, and suggest they pick something from the ephemeral port range rather than port 53. This means that the example will not work if it is merely uncommented, but this will hopefully encourage users to read the comment.
* Merge from vendor/bind9/dist as of the 9.4.2-P1 import, includingdougb2008-07-1215-36620/+2567
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the patch from ISC for lib/bind9/check.c and deletion of unused files in lib/bind. This version will by default randomize the UDP query source port (and sequence number of course) for every query. In order to take advantage of this randomization users MUST have an appropriate firewall configuration to allow UDP queries to be sent and answers to be received on random ports; and users MUST NOT specify a port number using the query-source[-v6] options. The avoid-v[46]-udp-ports options exist for users who wish to eliminate certain port numbers from being chosen by named for this purpose. See the ARM Chatper 6 for more information. Also please note, this issue applies only to UDP query ports. A random ephemeral port is always chosen for TCP queries. This issue applies primarily to name servers whose main purpose is to resolve random queries (sometimes referred to as "caching" servers, or more properly as "resolving" servers), although even an "authoritative" name server will make some queries, primarily at startup time. All users of BIND are strongly encouraged to upgrade to the latest version, and to utilize the source port randomization feature. This update addresses issues raised in: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447 http://www.kb.cert.org/vuls/id/800113 http://tools.ietf.org/html/draft-ietf-dnsext-forgery-resilience
* The vendor area is the proper home for these files now.dougb2008-07-122-187/+0
|
* A number of significant enhancements to the ciss driver:scottl2008-07-114-150/+494
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. The FreeBSD driver was setting an interrupt coalesce delay of 1000us for reasons that I can only speculate on. This was hurting everything from lame sequential I/O "benchmarks" to legitimate filesystem metadata operations that relied on serialized barrier writes. One of my filesystem tests went from 35s to complete down to 6s. 2. Implemented the Performant transport method. Without the fix in (1), I saw almost no difference. With it, my filesystem tests showed another 5-10% improvement in speed. It was hard to measure CPU utilization in any meaningful way, so it's not clear if there was a benefit there, though there should have been since the interrupt handler was reduced from 2 or more PCI reads down to 1. 3. Implemented MSI-X. Without any docs on this, I was just taking a guess, and it appears to only work with the Performant method. This could be a programming or understanding mistake on my part. While this by itself made almost no difference to performance since the Performant method already eliminated most of the synchronous reads over the PCI bus, it did allow the CISS hardware to stop sharing its interrupt with the USB hardware, which in turn allowed the driver to become decoupled from the Giant-locked USB driver stack. This increased performance by almost 20%. The MSI-X setup was done with 4 vectors allocated, but only 1 vector used since the performant method was told to only use 1 of 4 queues. Fiddling with this might make it work with the simpleq method, not sure. I did not implement MSI since I have no MSI-specific hardware in my test lab. 4. Improved the locking in the driver, trimmed some data structures. This didn't improve test times in any measurable way, but it does look like it gave a minor improvement to CPU usage when many processes/threads were doing I/O in parallel. Again, this was hard to accurately test.
* Don't leak DMA map if not freed.delphij2008-07-111-0/+2
| | | | Submitted by: kevlo
* Dust off old code for support of USB isochronous transfers.emax2008-07-113-215/+341
| | | | | | | | | USB isochronous transfer support is required for Bluetooth SCO. While i'm here change u_int to uint and update TODO. This should produce no visible changes unless the device is broken (or really old). MFC after: 3 months
* - Fix a logic error when updating plex configuration.lulf2008-07-111-1/+2
| | | | Approved by: pjd (mentor)
* Put the _cpuset* symbols in FBSDprivate_1.0 instead of trying to putbrooks2008-07-111-5/+5
| | | | nonexistant __cpuset* there.
* Improve readability and cscope searches a little bit by not using theobrien2008-07-111-38/+38
| | | | same variable name in closely related (but not conflicting) contexts.
* Use the VM_ALLOC_INTERRUPT for the page requests when allocating memorykib2008-07-111-7/+5
| | | | | | | | | | | | | | | for the bio for swapout write. It allows the page allocator to drain free page list deeper. As result, a deadlock where pageout deamon sleeps waiting for bio to be allocated for swapout is no more reproducable in practice. Alan said that M_USE_RESERVE shall be ressurrected and used there, but until this is implemented, M_NOWAIT does exactly what is needed. Tested by: pho, kris Reviewed by: alc No objections from: phk MFC after: 2 weeks (RELENG_7 only)
* Make it atomic for the devfs_populate_loop() to see the setting ofkib2008-07-111-1/+2
| | | | | | | | | | | | SI_ALIAS flag and initialization of the si_parent when alias is created. Assert that supplied parent device is not NULL. Both situations could cause NULL dereference in the devfs_populate_loop() when creating a symlink for SI_ALIAS'ed device. Namely, cdp->cdp_c.si_parent may be NULL. Reported by: mav MFC after: 2 weeks
* The pfctl(8) program is already pretty verbose, so don't print extramtm2008-07-111-2/+2
| | | | information in quiet mode.
* Revert r180431.obrien2008-07-112-51/+47
| | | | r180431 broke the AMD64 build (the only arch using kern/link_elf_obj.c)
OpenPOWER on IntegriCloud