summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix a few typos for s25fl types.loos2013-08-281-2/+2
| | | | Approved by: adrian (mentor)
* Make ar71xx_spi attach the next free unit of spibus and not only spibus0.loos2013-08-281-1/+1
| | | | Approved by: adrian (mentor)
* Add the default hints to make the GPIO pins, rf led and reset switch workloos2013-08-281-0/+18
| | | | | | | | out of the box on RouterStation. PR: 177832 Submitted by: Petko Bordjukov (bordjukov@gmail.com) Approved by: adrian (mentor)
* Properly free gpiobus ivars when gpiobus_parse_pins() fails and also onloos2013-08-281-4/+18
| | | | | | | gpiobus detachment. Suggested by: imp Approved by: adrian (mentor)
* Support the PCI-Express SSD in the new MacBook Air (model A1465)gavin2013-08-281-0/+1
| | | | | Submitted by: Johannes Lundberg <johannes brilliantservice.co.jp> MFC after: 3 days
* Take a very small step toward the Century of the Anchovy by increasing theivoras2013-08-281-1/+1
| | | | | time dirhash entries stay in memory before being considered for eviction to 1 minute.
* Fix 'make depend'uqs2013-08-281-1/+1
|
* mdoc fixjoel2013-08-281-1/+1
|
* Fix GT PCI controller driver on big-endian hardwaregonzo2013-08-281-18/+35
|
* Previously, both zfs_rename and zfs_link does a check on whetherdelphij2013-08-281-3/+11
| | | | | | | | | | | | | | | | | | | | | | the passed vnode belongs to the same mount point (v_vfsp or also known as v_mount in FreeBSD). This check prevents the code from proceeding further on vnodes that do not belong to ZFS, for instance, on UFS or NULLFS. The recent change (merged as r254585) on upstream changes the check of v_vfsp to instead check the znode's z_zfsvfs. On Illumos this would work because when the vnode comes from lofs, the VOP_REALVP() would give the right vnode, this is not true on FreeBSD where our VOP_REALVP is a no-op, and as such tdvp is not guaranteed to be a ZFS vnode, and will later trigger a failed assertion when verifying the vnode. This changeset modifies our local shims (zfs_freebsd_rename and zfs_freebsd_link) to check if v_mount matches before proceeding further. Reported by: many Diagnostic work by: avg
* Really regen after r254962.zeising2013-08-271-7/+4
| | | | | | | This removes the WITH_BSDCONFIG description alltogether, since this option is removed. At the same time, fix the WITHOUT_LIBCPLUSPLUS option that had gotten inverted.
* Use .SHELL to tell bmake to use 'set -e' when running scriptssjg2013-08-271-6/+20
| | | | | | | | since most FreeBSD makefiles it is in effect. Move the other bmake compatability knobs out of the POSIX block. Reviewed by: obrien
* Fix a typo introduced in r254975.jkim2013-08-271-1/+1
|
* wordexp(): Avoid leaking the pipe file descriptors to a parallel fork/exec.jilles2013-08-271-4/+4
| | | | This uses the new pipe2() system call added on May 1 (r250159).
* Fix bug in Flash access codedavidcs2013-08-271-5/+5
| | | | Submitted by: David C Somayajulu
* Install 450.status-security.jlh2013-08-271-1/+2
|
* Make the period of each periodic security script configurable.jlh2013-08-2721-125/+476
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are now six additional variables weekly_status_security_enable weekly_status_security_inline weekly_status_security_output monthly_status_security_enable monthly_status_security_inline monthly_status_security_output alongside their existing daily counterparts. They all have the same default values. All other "daily_status_security_${scriptname}_${whatever}" variables have been renamed to "security_status_${name}_${whatever}". A compatibility shim has been introduced for the old variable names, which we will be able to remove in 11.0-RELEASE. "security_status_${name}_enable" is still a boolean but a new "security_status_${name}_period" allows to define the period of each script. The value is one of "daily" (the default for backward compatibility), "weekly", "monthly" and "NO". Note that when the security periodic scripts are run directly from crontab(5) (as opposed to being called by daily or weekly periodic scripts), they will run unless the test is explicitely disabled with a "NO", either for in the "_enable" or the "_period" variable. When the security output is not inlined, the mail subject has been changed from "$host $arg run output" to "$host $arg $period run output". For instance: myfbsd security run output -> myfbsd security daily run output I don't think this is considered as a stable API, but feel free to correct me if I'm wrong. Finally, I will rearrange periodic.conf(5) and default/periodic.conf to put the security options in their own section. I left them in place for this commit to make reviewing easier. Reviewed by: hackers@
* Pad m_hdr on 32bit architectures to to prevent alignment and paddingandre2013-08-272-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | problems with the way MLEN, MHLEN, and struct mbuf are set up. CTASSERT's are provided to detect such issues at compile time in the future. The #define MLEN and MHLEN calculation do not take actual compiler- induced alignment and padding inside the complete struct mbuf into account. Accordingly appropriate attention is required when changing members of struct mbuf. Ideally one would calculate MLEN as (MSIZE - sizeof(((struct mbuf *)0)->m_hdr) but that doesn't work as the compiler refuses to operate on an as of yet incomplete structure. In particular ARM 32bit has more strict alignment requirements which caused 4 bytes of padding between m_hdr and pkthdr in struct mbuf because of the 64bit members in pkthdr. This wasn't picked up by MLEN and MHLEN causing an overflow of the mbuf provided data storage by overestimating its size. I386 didn't show this problem because it handles unaligned access just fine, albeit at a small performance penalty. On 64bit architectures the struct mbuf layout is 64bit aligned in all places. Reported by: Thomas Skibo <ThomasSkibo-at-sbcglobal-dot-net> Tested by: tuexen, ian, Thomas Skibo (extended patch) Sponsored by: The FreeBSD Foundation
* If a drive returns ASC/ASCQ 0x04,0x11 "Logical unit not ready,ken2013-08-271-1/+1
| | | | | | | | | | | | | | | | | | | notify (enable spinup) required", instead of doing the normal retries, poll for a change in status. We will poll every half second for a minute for the status to change. Hitachi drives (and likely other SAS drives) return that ASC/ASCQ when they are waiting to spin up. What it means is that they are waiting for the SAS expander to send them the SAS NOTIFY (ENABLE SPINUP) primitive. That primitive is the mechanism expanders/enclosures use to sequence drive spinup to avoid overloading power supplies. Sponsored by: Spectra Logic MFC after: 3 days
* * s_erf.c:kargl2013-08-272-99/+71
| | | | | | | | | | | | | | | | | | | | | | . Use integer literal constants instead of double literal constants. * s_erff.c: . Use integer literal constants instead of casting double literal constants to float. . Update the threshold values from those carried over from erf() to values appropriate for float. . New sets of polynomial coefficients for the rational approximations. These coefficients have little, but positive, effect on the maximum error in ULP in the four intervals, but do improve the overall speed of execution. . Remove redundant GET_FLOAT_WORD(ix,x) as hx already contained the contents that is packed into ix. . Update the mask that is used to zero-out lower-order bits in x in the intervals [1.25, 2.857143] and [2.857143, 12]. In tests on amd64, this change improves the maximum error in ULP from 6.27739 and 63.8095 to 3.16774 and 2.92095 on these intervals for erffc(). Reviewed by: bde
* Remove duplicate dev.xbd.*.max_requests sysctl added in r252260.cperciva2013-08-271-4/+0
| | | | Approved by: gibbs
* Assemble linux32_locore.s and ia32_sigtramp.S with clang integrated assembler.rdivacky2013-08-272-6/+0
| | | | | | Support for .code32 and .code64 in llvm was implemented more than 2 years ago. Tested by: Dan McGregor <dan.mcgregor at usask dot ca>
* Allow single byte reads of the emulated MSI-X tables. This is not requiredneel2013-08-271-3/+9
| | | | | by the PCI specification but needed to dump MMIO space from "ddb" in the guest.
* Add support for emulating the byte move instruction "mov r/m8, r8".neel2013-08-271-2/+10
| | | | | This emulation is required when dumping MMIO space via the ddb "examine" command.
* Remove include opt_ofed.h since OFED is unifdef'd.alfred2013-08-271-2/+0
| | | | Pointed out by: glebius
* Formally remove WITH_BSDCONFIG build option and re-generate src.conf.5dteske2013-08-272-6/+4
| | | | NOTE: Should have been inline with revisions 252862 and 254958.
* Add note/reminder about dialog(1) regression in HEAD/10.0-C so that we don'tdteske2013-08-271-0/+13
| | | | forget about it in the multi-month run of things to fix prior to 10.0-R.
* Make the PAM password strength checking module WARNS=2 safe.will2013-08-272-17/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | lib/libpam/modules/pam_passwdqc/Makefile: Bump WARNS to 2. contrib/pam_modules/pam_passwdqc/pam_passwdqc.c: Bump _XOPEN_SOURCE and _XOPEN_VERSION from 500 to 600 so that vsnprint() is declared. Use the two new union types (pam_conv_item_t and pam_text_item_t) to resolve strict aliasing violations caused by casts to comply with the pam_get_item() API taking a "const void **" for all item types. Warnings are generated for casts that create "type puns" (pointers of conflicting sized types that are set to access the same memory location) since these pointers may be used in ways that violate C's strict aliasing rules. Casts to a new type must be performed through a union in order to be compliant, and access must be performed through only one of the union's data types during the lifetime of the union instance. Handle strict-aliasing warnings through pointer assignments, which drastically simplifies this change. Correct a CLANG "printf-like function with more arguments than format" error. Submitted by: gibbs Sponsored by: Spectra Logic
* Allow more space for interface names.gavin2013-08-271-2/+2
| | | | MFC after: 1 week
* It was brought to my attention that SVN r252862 was incomplete. It neededdteske2013-08-271-1/+0
| | | | to also make this change, to completely deprecate WITH_BSDCONFIG.
* Use the new ieee80211_tx_complete() function.adrian2013-08-271-11/+2
|
* Create a new function to complete 802.11 mbuf transmission.adrian2013-08-272-0/+33
| | | | | | | | | | | | | | | | | The aim of this function is to eventually be the completion entry point for all 802.11 encapsulated mbufs. All the wifi drivers end up doing what is in this function so it's an easy win to turn it into a net80211 method and abstract out this code. Ideally the drivers will all eventually be modified to queue up completed mbufs and call this function with all the driver locks not held. This will allow for some much more interesting software queue handling in the future (like net80211 based A-MSDU, fast-frames, A-MPDU aggregation and retransmission.) Tested: * ath(4), iwn(4)
* Fix a crash when reloading the configuration file.hrs2013-08-271-4/+2
| | | | Spotted by: des
* Add missing newlines to Fibre Channel attributes output.mav2013-08-271-3/+3
|
* Update copyright.dteske2013-08-271-1/+1
|
* Fix 'make release' on older hosts: use buildworld legacy utilities.will2013-08-271-0/+5
| | | | | | | | | | | Newer FreeBSD installs require an install(1) that supports the new flags. This adds ${MAKEOBJDIRPREFIX}${.CURDIR}/tmp/legacy/{bin,usr/{bin,sbin}} to the PATH while generating an mtree database for 'make release'. Note that the problem only exists here because mm-mtree.sh generates its own object tree to avoid mucking with the existing one, which results in a PATH containing legacy utility dirs that are empty.
* Couple minor if_vmx tweaksbryanv2013-08-272-30/+32
| | | | | | | | | | | | - Use queue size fields from the Tx/Rx queues in various places instead of (currently the same values) from the softc. - Fix potential crash in detach if the attached failed to alloc queue memory. - Move the VMXNET3_MAX_RX_SEGS define to a better spot. - Tweak frame size calculation w.r.t. ETHER_ALIGN. This could be tweaked some more, or removed since it probably doesn't matter much for x86 (and the x86 class of machines this driver will be used on).
* Build all ZFS testing & debugging tools with -g.will2013-08-273-6/+10
| | | | | | These programs and everything using libzpool rely on the embedded asserts to verify the correctness of operations. Given that, the core dumps would be useless without debug symbols.
* Fix off-by-1 error in assert.grehan2013-08-271-1/+1
| | | | Submitted by: Tycho Nightingale (tycho.nightingale@pluribusnetworks.com)
* Fixes for compatibility with QEMU:gonzo2013-08-271-2/+8
| | | | | | | | - Route PCI interrupt for NIC - Make "no mapping" warning more user-friendly: add device name and mention that it's IRQ mapping - Do not overlap ICUs' IO window with PCI devices' IO windows by starting IO rman at offset 0x100
* When allocating a pbuf for the cluster write, do not sleep waitingkib2013-08-271-1/+3
| | | | | | | | | | | for the available pbuf when passed vnode is backing md(4). Other i/o directed to the same md device might already hold pbufs, and then we could deadlock since only our progress can free a pbuf needed for wakeup. Obtained from: projects/vm6 Reminded and tested by: pho MFC after: 1 week
* - Initialize freq variable so we will not end up with random valuegonzo2013-08-271-0/+1
| | | | if there is no YAMON present
* Add the ability to display the default FIB number for a process to thewill2013-08-265-1/+9
| | | | | | | | | | | | | | | | | | ps(1) utility, e.g. "ps -O fib". bin/ps/keyword.c: Add the "fib" keyword and default its column name to "FIB". bin/ps/ps.1: Add "fib" as a supported keyword. sys/compat/freebsd32/freebsd32.h: sys/kern/kern_proc.c: sys/sys/user.h: Add the default fib number for a process (p->p_fibnum) to the user land accessible process data of struct kinfo_proc. Submitted by: Oliver Fromme <olli@fromme.com>, gibbs
* Building upon SVN r254237, disable automated activation of alternate layoutsdteske2013-08-263-19/+34
| | | | | | | | | | and add support for default underride to $loader_version, acting as a way to name a release. Release text is not displayed for the aforementioned feature of alternate display layout (introduced in r254237); however, for all other layouts (incl. default), the release name is displayed at lower-right. See version.4th(8) for additional information and/or historical details. NOTE: Also a minor edit to version.4th(8) while we're here.
* Merge various CTF fixes from illumospfg2013-08-261-5/+65
| | | | | | | | | | | | | | | 2942 CTF tools need to handle files which legitimately lack data 2978 ctfconvert still needs to ignore legitimately dataless files on SPARC Illumos Revisions: 13745:6b3106b4250f 13754:7231b684c18b Reference: https://www.illumos.org/issues/2942 https://www.illumos.org/issues/2978 MFC after: 3 weeks
* Reimplement the FDOPT_NOERROR feature that was kicked out in r134081.joerg2013-08-261-5/+18
| | | | | | | | | | It is needed for fdread(1) in order to be able to recover from CRC errors in the data field of a floppy sector (by returning the sector data that failed CRC, rather than inventing dummy data). When closing the device, clear all transient device options. MFC after: 1 week
* MFprojects/camlock r254895:mav2013-08-261-4/+28
| | | | Add unmapped BIO support to GEOM ZERO if kern.geom.zero.clear is cleared.
* Use correct mailbox and PCIe PF number when querying RDMA parameters.np2013-08-261-1/+1
|
* fix up some comments and a white space issue...jmg2013-08-261-6/+6
| | | | MFC after: 3 days
* fix up my copyright and remove third clause..jmg2013-08-261-5/+1
|
OpenPOWER on IntegriCloud