summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Explicitly initialize the packet buffer to NULL after we unmap the zero copycsjp2011-06-031-0/+1
| | | | | | | | | | | | | buffers. This fixes a segfault on exit due to calling free on a bogus pointer. This should be considered a temporary stop gap fix to avoid the crash. The complete fix re-shuffles the initializations of some of the clean-up pointers. The details of the fix can be found in the libpcap git repository: commit bc8209b71e928870b0f172d43b174ab27ba24394 Proded by: kevlo, rpaulo MFC after: 2 weeks Submitted by: Anton Yuzhaninov
* When MANCOLOR environment variable is set, enable ANSI color escapesru2011-06-032-13/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in grotty(1). This makes it possible to view colorized manpages in color. When MANPAGER environment variable is set, use it instead of PAGER. Why another environment variable, one might ask? With color output enabled, both a terminal and a pager should support the ANSI color escapes. On a supporting terminal, less(1) with option -R would be such a pager, while "more -s" (the current default pager for man(1)) will show garbage. It means a different default pager is needed when color output is enabled, but many people have PAGER set customary, and it's unlikely to support ANSI color escapes, so introducing yet another variable (MANPAGER) seemed like a good option to me: - if MANPAGER is set, use that unconditionally; - if you disable color support (it is by default), and don't set MANPAGER, you get an old behavior: -P pager, $PAGER, "more -s", in that order; - if you enable color support (by setting MANCOLOR), and don't set MANPAGER, we ignore PAGER which is unlikely to support ANSI color escapes, and you get: -P pager, "less -Rs", in that order; - you might have good reasons for different man(1) and general purpose pagers; - later versions of GNU man(1) support MANPAGER.
* Update disk's stripesize and stripeoffset parameters on provider open.mav2011-06-031-0/+6
| | | | | | | | | They are media-dependent and may change in run-time, same as sectorsize and/or mediasize. SCSI devices return physical sector size and offset via READ CAPACITY(16) command and so can not report it until media inserted or at least until probe sequence completed. UNMAP support is also reported there.
* Properly return an ENOBUFS error if a write to a tun(4) device failsjhb2011-06-031-10/+7
| | | | | | | | | | | due to m_uiotombuf() failing. While here, trim unneeded error handling related to tuninit() since it can never fail. Submitted by: Martin Birgmeier la5lbtyi aon at Reviewed by: glebius MFC after: 1 week
* Don't use col(1) since grotty(1) never outputs reverse line feeds,ru2011-06-032-15/+6
| | | | | | | and because col(1) mangles ANSI color escapes if enabled. Spaces to tabs compression is now done by passing -h to grotty(1). Discussed with: uqs
* Re-enable SGR support (ANSI color escapes) in grotty(1) by default.ru2011-06-031-8/+0
| | | | | | | Our man(1) and bsd.doc.mk still disable it for POLA reasons via the -c option to grotty(1). PR: gnu/82353
* Don't pass -o1- to groff(1) by default. If ms(7) formatted documentru2011-06-031-4/+2
| | | | | | | | | | | uses the .RP macro, a separate cover page is created as page 0 which is not otherwise output. The bug was hiding by a hack in troffrc that disables SGR support in grotty(1), which I'm going to remove now. For POLA reasons, still disable SGR support in grotty(1), by passing -P-c to groff(1). If we want SGR sequences in these documents, this can be removed. MFC after: 1 week
* Generally clean up markup.ru2011-06-031-71/+85
|
* Bring over the relevant registers to use when implementing the quiet timeadrian2011-06-038-0/+63
| | | | | | | | | portion of 802.11h. The AR5212 code has been brought over as a reference, it's currently untested. Obtained from: Atheros
* Increase maximum supported number of ranges per TRIM command from 256 to 512mav2011-06-031-2/+2
| | | | | to use full potential of Intel X25-M SSDs. On synthetic test with 32K ranges it gives about 20% speedup, which probably costs more then 2K of RAM.
* Add diagnostic message about not aligned partitions.ae2011-06-031-1/+16
| | | | Idea from: ivoras
* Trim more when parsing MANCONFIG directive.ru2011-06-031-1/+1
|
* Typo.ru2011-06-031-1/+1
|
* Added support for the MANWIDTH environment variable:ru2011-06-032-2/+46
| | | | | | | If set to a numeric value, used as the width manpages should be displayed. Otherwise, if set to a special value ``tty'', and output is to a terminal, the pages may be displayed over the whole width of the screen.
* Quantities stored on the stack on ppc64 tend to be twice as large as onnwhitehorn2011-06-031-1/+1
| | | | ppc32, so make the early stack correspondingly twice as big.
* Always use LCM when stripesize > 0.ae2011-06-021-2/+2
|
* Use stripesize and stripeoffset in the automatic calculation ofae2011-06-021-18/+33
| | | | | | | | | | partition offsets. If user requests specific alignment and provider's stripesize is not zero, then use a least common multiple from the stripesize and user specified value. Also fix "gpart resize" implementation: do not try to align the partition size, because the start offset may be not aligned. Instead align the end offset and then calculate size. Also use stripesize and stripeoffset for "gpart resize" command.
* When possible, join ranges of subsequest BIO_DELETE requests to handle moremav2011-06-021-9/+25
| | | | | | | | | (up to 2048 instead of 256 or even 64) of them with single TRIM request. OCZ Vertex2/Vertex3 SSDs can handle no more then 64 ranges per TRIM request. Due to lack of BIO_DELETE clustering now, it means that we could delete no more then 2MB per request (on FS with 32K block) with limited request rate. This change increases delete rate on Vertex2 from 250MB/s to 950MB/s.
* Fix the nfs related daemons so that they don't intermittentlyrmacklem2011-06-021-28/+212
| | | | | | | | | | | | | | | | | | | | | | | | fail with "bind: address already in use". This problem was reported to the freebsd-stable@ mailing list on Feb. 19 under the subject heading "statd/lockd startup failure" by george+freebsd at m5p dot com. The problem is that the first combination of {udp,tcp X ipv4,ipv6} would select a port# dynamically, but one of the other three combinations would have that port# already in use. The patch is somewhat involved because it was requested by dougb@ that the four combinations use the same port# wherever possible. The patch splits the create_service() function into two functions. The first goes as far as bind(2) in a loop for up to GETPORT_MAXTRY - 1 times, attempting to use the same port# for all four cases. If these attempts fail, the last attempt allows the 4 cases to use different port #s. After this function has succeeded, the second function, called complete_service(), does the rest of what create_service() did. The three daemons mountd, rpc.lockd and rpc.statd all have a create_service() function that is patched in a similar way. However, create_service() has non-trivial differences for the three daemons that made it impractical to share the same functions between them. Reviewed by: jhb MFC after: 2 weeks
* Fix the nfs related daemons so that they don't intermittentlyrmacklem2011-06-021-28/+221
| | | | | | | | | | | | | | | | | | | | | | | | fail with "bind: address already in use". This problem was reported to the freebsd-stable@ mailing list on Feb. 19 under the subject heading "statd/lockd startup failure" by george+freebsd at m5p dot com. The problem is that the first combination of {udp,tcp X ipv4,ipv6} would select a port# dynamically, but one of the other three combinations would have that port# already in use. The patch is somewhat involved because it was requested by dougb@ that the four combinations use the same port# wherever possible. The patch splits the create_service() function into two functions. The first goes as far as bind(2) in a loop for up to GETPORT_MAXTRY - 1 times, attempting to use the same port# for all four cases. If these attempts fail, the last attempt allows the 4 cases to use different port #s. After this function has succeeded, the second function, called complete_service(), does the rest of what create_service() did. The three daemons mountd, rpc.lockd and rpc.statd all have a create_service() function that is patched in a similar way. However, create_service() has non-trivial differences for the three daemons that made it impractical to share the same functions between them. Reviewed by: jhb MFC after: 2 weeks
* Fix the nfs related daemons so that they don't intermittentlyrmacklem2011-06-021-30/+213
| | | | | | | | | | | | | | | | | | | | | | | | fail with "bind: address already in use". This problem was reported to the freebsd-stable@ mailing list on Feb. 19 under the subject heading "statd/lockd startup failure" by george+freebsd at m5p dot com. The problem is that the first combination of {udp,tcp X ipv4,ipv6} would select a port# dynamically, but one of the other three combinations would have that port# already in use. The patch is somewhat involved because it was requested by dougb@ that the four combinations use the same port# wherever possible. The patch splits the create_service() function into two functions. The first goes as far as bind(2) in a loop for up to GETPORT_MAXTRY - 1 times, attempting to use the same port# for all four cases. If these attempts fail, the last attempt allows the 4 cases to use different port #s. After this function has succeeded, the second function, called complete_service(), does the rest of what create_service() did. The three daemons mountd, rpc.lockd and rpc.statd all have a create_service() function that is patched in a similar way. However, create_service() has non-trivial differences for the three daemons that made it impractical to share the same functions between them. Reviewed by: jhb MFC after: 2 weeks
* Temporarily back out those parts of r222613 related to parsing the memorynwhitehorn2011-06-021-144/+25
| | | | | map. They cause non-understood boot failures on some Apple machines with more than 2 GB of RAM (like my work desktop).
* The POWER7 has only 32 SLB slots instead of 64, like other supportednwhitehorn2011-06-024-44/+52
| | | | | | 64-bit PowerPC CPUs. Add infrastructure to support variable numbers of SLB slots and move the user slot from 63 to 0, so that it is always available.
* Write the multi step netconfig to a temporary file and only move thatbz2011-06-023-9/+10
| | | | | | | | | | to the final name if netconfig was completely finished. This fixes reentrance problems even better than r222611. Suggested by: nwhitehorn Reviewed by: nwhitehorn Sponsored by: The FreeBSD Foundation Sponsored by: iXsystems
* If running under a hypervisor, don't yell at the user about startingnwhitehorn2011-06-021-1/+4
| | | | | unknown CPU types, instead relying on the hypervisor to have given us a reasonable environment.
* Missed file in r222613.nwhitehorn2011-06-021-1/+4
|
* Explicitly initialize the first thread's MSR to PSL_KERNSET.nwhitehorn2011-06-021-1/+1
|
* Include the modules area in the mapped kernel code. This fixes the kernel'snwhitehorn2011-06-021-3/+2
| | | | | access to modules and loader metadata when started from real mode, but without a direct map.
* Remove some dead code: unnecessary isyncs and memory sorting, which arenwhitehorn2011-06-024-47/+9
| | | | handled in mtmsr() and mem_regions(), respectively.
* MFpseries:nwhitehorn2011-06-029-187/+898
| | | | | | | | | | Renovate and improve the AIM Open Firmware support: - Add RTAS (Run-Time Abstraction Services) support, found on all IBM systems and some Apple ones - Improve support for 32-bit real mode Open Firmware systems - Pull some more OF bits over from the AIM directory - Fix memory detection on IBM LPARs and systems with more than one /memory node (by andreast@)
* Empty the network configuration only after the user decided to pick anbz2011-06-021-2/+2
| | | | | | | | | | interface. Otherwise an accidental start of the netowrk configuration and immediate cancel after the install has finished removes the previously configured settings. Discussed with: nwhitehorn Sponsored by: The FreeBSD Foundation Sponsored by: iXsystems
* Fix opening a shell on the new system (prevent the shell's stderr fromnwhitehorn2011-06-021-1/+1
| | | | ending up in the install log).
* Do not hide stripeoffset from libgeom(3), it may be useful even whenae2011-06-021-4/+2
| | | | | | stripesize is zero. MFC after: 1 week
* Do not leak the pcbinfohash lock in the case where in6_pcbladdr() returnsrwatson2011-06-021-1/+1
| | | | | | | an error during TCP connect(2) on an IPv6 socket. Submitted by: bz Sponsored by: Juniper Networks, Inc.
* Fix man -t by not passing grotty flags to groff when grotty is notuqs2011-06-021-1/+1
| | | | | | | | involved. This fixes a regression introduced with r221303. Noticed by: jilles
* mdoc: reorder sections consistentlyuqs2011-06-0211-90/+91
|
* mdoc: fix markupuqs2011-06-024-4/+6
|
* Cut and paste mistake corrected.jfv2011-06-021-1/+1
|
* There are a couple of structs in mfireg.h with members named 'class'.emaste2011-06-023-15/+15
| | | | | | | | | | These cause problems when trying to include the header in a C++ project. Rename them to 'evt_class', and track the change in mfi and mfiutil. Submitted by: Mark Johnston Sponsored by: Sandvine Incorporated Reviewed by: jhb@ MFC after: 1 week
* First off: update the driver README, the old one was horriblyjfv2011-06-024-149/+257
| | | | | | | | | | | | | | | | | crusty, and this still isn't perfect, but its at least a bit more recent. Secondly, a few improvements to the driver from Andrew Boyer, support hint to allow devices to not attach, add VLAN_HWTSO capability so vlans can use TSO, fix in the interrupt handler to make sure the stack TX queue is processed. Oh, and also make sure IPv6 does not cause a re-init in the ioctl routine. Thanks for your efforts Andrew! Thanks to Claudio Jeker for noticing the ixgbe_xmit() routine was not correctly swapping the dma map from the first to the last descriptor in a multi-descriptor transmission, corrected this.
* In the VOP_PUTPAGES() implementations, change the default error fromkib2011-06-017-34/+48
| | | | | | | | | | | | | | | | VM_PAGER_AGAIN to VM_PAGER_ERROR for the uwritten pages. Return VM_PAGER_AGAIN for the partially written page. Always forward at least one page in the loop of vm_object_page_clean(). VM_PAGER_ERROR causes the page reactivation and does not clear the page dirty state, so the write is not lost. The change fixes an infinite loop in vm_object_page_clean() when the filesystem returns permanent errors for some page writes. Reported and tested by: gavin Reviewed by: alc, rmacklem MFC after: 1 week
* Flesh out the radar detection related operations for the ath driver.adrian2011-06-016-1/+281
| | | | | | | | | | | | | | | | | | | | | | | | | This is in no way a complete DFS/radar detection implementation! It merely creates an abstracted interface which allows for future development of the DFS radar detection code. Note: Net80211 already handles the bulk of the DFS machinery, all we need to do here is figure out that a radar event has occured and inform it as such. It then drives the DFS state engine for us. The "null" DFS radar detection module is included by default; it doesn't require a device line. This commit: * Adds a simple abstracted layer for radar detection state - sys/dev/ath/ath_dfs/; * Implements a null DFS module which doesn't do anything; (ie, implements the exact behaviour at the moment); * Adds hooks to the ath driver to process received radar events and gives the DFS module a chance to determine whether a radar has been detected. Obtained from: Atheros
* Add some missing DFS chipset functionality to the FreeBSD HAL.adrian2011-06-0116-1/+242
| | | | | | | | | | | | | | | | | | | | | | | | Please note - this doesn't in any way constitute a full DFS implementation, it merely adds the relevant capability bits and radar detection threshold register access. The particulars: * Add new capability bits outlining what the DFS capabilities are of the various chipsets. * Add HAL methods to set and get the radar related register values. * Add AR5212 and AR5416+ DFS radar related register value routines. * Add a missing HAL phy error code that's related to radar event processing. * Add HAL_PHYERR_PARAM, a data type that encapsulates the radar register values. The AR5212 routines are just for completeness. The AR5416 routines are a super-set of those; I may later on do a drive-by pass to tidy up duplicate code. Obtained from: Linux, Atheros
* Add an optional netisr dispatch point at ether_input(), but set therwatson2011-06-011-1/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | default dispatch method to NETISR_DISPATCH_DIRECT in order to force direct dispatch. This adds a fairly negligble overhead without changing default behavior, but in the future will allow deferred or hybrid dispatch to other worker threads before link layer processing has taken place. For example, this could allow redistribution using RSS hashes without ethernet header cache line hits, if the NIC was unable to adequately implement load balancing to too small a number of input queues -- perhaps due to hard queueset counts of 1, 3, or 8, but in a modern system with 16-128 threads. This can happen on highly threaded systems, where you want want an ithread per core, redistributing work to other queues, but also on virtualised systems where hardware hashing is (or is not) available, but only a single queue has been directed to one VCPU on a VM. Note: this adds a previously non-present assertion about the equivalence of the ifnet from which the packet is received, and the ifnet stamped in the mbuf header. I believe this assertion to generally be true, but we'll find out soon -- if it's not, we might have to add additional overhead in some cases to add an m_tag with the originating ifnet pointer stored in it. Reviewed by: bz MFC after: 3 weeks Sponsored by: Juniper Networks, Inc.
* O_FORWARD_IP is only action which depends from the result of lookup ofae2011-06-011-1/+2
| | | | | | | | | | | | | | | | | | | | | dynamic rules. We are doing forwarding in the following cases: o For the simple ipfw fwd rule, e.g. fwd 10.0.0.1 ip from any to any out xmit em0 fwd 127.0.0.1,3128 tcp from any to any 80 in recv em1 o For the dynamic fwd rule, e.g. fwd 192.168.0.1 tcp from any to 10.0.0.3 3333 setup keep-state When this rule triggers it creates a dynamic rule, but this dynamic rule should forward packets only in forward direction. o And the last case that does not work before - simple fwd rule which triggers when some dynamic rule is already executed. PR: kern/147720, kern/150798 MFC after: 1 month
* Poke correct GPIO pins for newer axe(4) controllers with Marvellyongari2011-06-011-3/+18
| | | | | | | PHY. Newer models seem to use different LED mode that requires enabling both GPIO1 and GPIO2. Tested by: marcel
* Add support for new USB serial driver.hselasky2011-06-0110-3/+1865
| | | | | Submitted by: Lev Serebryakov, lev @ MFC after: 14 days
* Don't try to close the stream if fopen(3) fails.jh2011-06-011-1/+1
| | | | | PR: bin/155349 Submitted by: Urankar Mikael
* Hide some debug messages under debug macro.ae2011-06-011-5/+5
| | | | MFC after: 1 week
* Hide useless warning under debug macro.ae2011-06-011-1/+2
| | | | | PR: kern/69963 MFC after: 1 week
OpenPOWER on IntegriCloud