summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* When using tcpdump -I -i wlanN and wlanN is not a monitor mode VAP,rpaulo2013-07-311-0/+23
| | | | | | tcpdump will print an error message saying rfmon is not supported. Give a concise explanation as to how one might solve this problem by creating a monitor mode VAP.
* Remove duplicate SRCS include block. Spotted by jmallett.jhibbits2013-07-311-5/+0
|
* Add the macio attachment for wi(4). Partially obtained from NetBSD.jhibbits2013-07-315-0/+203
| | | | | Reviewed by: adrian Obtained from: NetBSD (partially)
* Fix r253823. Some WIP patches snuck in.scottl2013-07-302-21/+7
| | | | Submitted by: zont
* Create a knob, kern.ipc.sfreadahead, that allows one to tune the amount ofscottl2013-07-303-9/+28
| | | | | | | readahead that sendfile() will do. Default remains the same. Obtained from: Netflix MFC after: 3 days
* Add a 'surrender' mode to fsck_ffs. With the -S flag, once hard read errorsscottl2013-07-303-2/+18
| | | | | | | | are encountered, the fsck will stop instead of wasting time chewing through possibly other errors. Obtained from: Netflix MFC after: 3 days
* MFV r253783:delphij2013-07-305-22/+110
| | | | | | | | | | | Skip eviction step of processing free records when doing ZFS receive to avoid the expensive search operation of non-existent dbufs in dn_dbufs. Illumos ZFS issues: 3834 incremental replication of 'holey' file systems is slow MFC after: 2 weeks
* MFV r253782:delphij2013-07-305-59/+114
| | | | | | | | | | | | | | | | | | | | | | | | To quote Illumos issue #3888: When 'zfs recv -F' is used with an incremental recv it rolls back any changes made since the last snapshot in case new changes were made to the file system while the recv is in progress (without -F the recv would fail when it does it's final check to commit the recv-ed data as the recv-ed data conflicts with the newly written data). However, if there is a snapshot taken after the recv began rolling back to the 'latest' snapshot will not help and the recv will still fail. 'zfs recv -F' should be extended to destroy any snapshots created since the source snapshot when finishing the recv (effectively rolling back through all snapshots, instead of just to the latest snapshot). Illumos ZFS issues: 3888 zfs recv -F should destroy any snapshots created since the incremental source MFC after: 2 weeks
* MFV r253781 + r253871:delphij2013-07-307-10/+39
| | | | | | | Illumos ZFS issues: 3894 zfs should not allow snapshot of inconsistent dataset MFC after: 2 weeks
* MFV r253784:smh2013-07-301-2/+2
| | | | | | | | | | | | Fix zfs send -D hang after processing requiring a CTRL+C to interrupt due to pthread_join prior to fd close. This was introduced by r251646 (MFV r251644) Illumos ZFS issue: 3909 "zfs send -D" does not work MFC after: 1 day
* MFV r253780:delphij2013-07-308-63/+164
| | | | | | | | | | | | | | | | | To quote Illumos #3875: The problem here is that if we ever end up in the error path, we drop the locks protecting access to the zfsvfs_t prior to forcibly unmounting the filesystem. Because z_os is NULL, any thread that had already picked up the zfsvfs_t and was sitting in ZFS_ENTER() when we dropped our locks in zfs_resume_fs() will now acquire the lock, attempt to use z_os, and panic. Illumos ZFS issues: 3875 panic in zfs_root() after failed rollback MFC after: 2 weeks
* MFC'ing to 9.2.obrien2013-07-301-1/+1
|
* Check for ipmi_attached in ipmi_isa_probe as a suggested alternative tosbruno2013-07-301-8/+8
| | | | | | | | ipmi_isa_attach. This keeps unintended but harmless noise about "ipmi1" from appearing in the boot up sequence. Submitted by: jbh@ (suggested by) Sponsored by: Yahoo! Inc.
* empirical testing showed that 3 seconds is just too slow for GET_DEVICE_IDsbruno2013-07-301-1/+1
| | | | | | | | | to return on newer Dell hardware. Bump to 6 second timeouts until someone has a better idea on how to handle this Reviewed by: jhb@ MFC after: 2 weeks Sponsored by: Yahoo! Inc.
* After discussions, revert svn r253708.sbruno2013-07-302-10/+11
| | | | | | | Changelog for 253708 was completely wrong and the code implemented something non-standard for the wrong reasons. Sponsored by: Yahoo! Inc.
* grep -i does not work for simple patterns and single byte locales, likeache2013-07-301-2/+2
| | | | | | | LANG=ru_RU.KOI8-R grep -i <some single KOI8-R letter> Fix it. MFC after: 3 days
* Fix a printf typo.scottl2013-07-301-1/+1
| | | | Obtained from: LSI
* Apply a casting sledgehammer.jhb2013-07-301-1/+1
| | | | Submitted by: dhw
* Unbreak sparc64 LINT. Need to fix this correctly at some point in the future.rpaulo2013-07-301-6/+6
|
* Allow three IOCTLs to be used on suspended pool, restoring state thatmav2013-07-301-3/+3
| | | | | | | | | | | | existed before IOCTL code refactoring merged change 4445fffb from illumos at r248571. This change allows `zpool clear` to be used again to recover suspended pool. It seems the only was supposed by the code to restore pool operation after reconnecting lost disks that were required for data completeness. There are still cases where `zpool clear` command can just safely stuck due to deadlocks inside ZFS kernel part, but probably that is better then having no chances to recover at all.
* Include an Accept header in requests.des2013-07-303-4/+20
| | | | | PR: kern/180917 MFC after: 1 week
* Add Michael Gmelin's name to the copyright statement.des2013-07-301-1/+2
|
* Add NO_RC16 quirk to make da driver avoid using READ CAPACITY(16) commandmav2013-07-301-3/+11
| | | | | if possible. Use it for Kingston JetFlash USB sticks, that are known to return garbage in response to that command.
* Pull in r186696 from upstream clang trunk:dim2013-07-301-2/+124
| | | | | | | | | | | | | | | | | This patch implements __get_cpuid_max() as an inline and __cpuid() and __cpuid_count() as macros to be compatible with GCC's cpuid.h. It also adds bit_<foo> constants for the various feature bits as described in version 039 (May 2011) of Intel's SDM Volume 2 in the description of the CPUID instruction. The list of bit_<foo> constants is a bit exhaustive (GCC doesn't do near this many). More bits could be added from a newer version of SDM if desired. Patch by John Baldwin! This should fix several ports which depend on this functionality being available. MFC after: 1 week
* Fix up paths after r253790.pluknet2013-07-301-2/+2
| | | | | | While here, use $? contraction. Reported by: O. Hartmann
* Move runfw to modules/usb.rpaulo2013-07-303-4/+9
| | | | | | While there, respect MK_SOURCELESS_UCODE. Discussed with: kevlo
* Import OpenBSD's rsu(4) WLAN driver.rpaulo2013-07-3010-1/+3521
| | | | | | | | | | | Support chipsets are the Realtek RTL8188SU, RTL8191SU, and RTL8192SU. Many thanks to Idwer Vollering for porting/writing the man page and for testing. Reviewed by: adrian, hselasky Obtained from: OpenBSD Tested by: kevlo, Idwer Vollering <vidwer at gmail.com>
* The errata 727915 requires a different workaround for r2p0, we have tocognet2013-07-291-13/+26
| | | | explicitely clean/invalidate every cache line using way/set operations.
* Remove useless cache operations.cognet2013-07-291-5/+0
|
* Decouple yarrow from random(4) device.obrien2013-07-295-0/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c comprise yarrow. * random(4) device doesn't really depend on rijndael-*. Yarrow, however, does. * Add random_adaptors.[ch] which is basically a store of random_adaptor's. random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah * Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones. * If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed. * Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one. Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: obrien
* Add a missing prototype.jhb2013-07-291-0/+1
| | | | Pointy hat: me
* Decouple yarrow from random(4) device.obrien2013-07-2981-140/+318
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c comprise yarrow. * random(4) device doesn't really depend on rijndael-*. Yarrow, however, does. * Add random_adaptors.[ch] which is basically a store of random_adaptor's. random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah * Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones. * If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed. * Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one. Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: obrien
* Unbreak sysctl ABI changes introduced in r253662zont2013-07-291-2/+4
| | | | Requested by: bde
* Various fixes to the mlxen(4) driver:jhb2013-07-291-21/+31
| | | | | | | | | | | | | | - Remove an incorrect assertion that can trigger when downing an interface. - Stop the interface during detach to avoid panics when unloading the driver. - A few locking fixes to be more consistent with other FreeBSD drivers: - Protect if_drv_flags with the driver lock, not atomic ops - Hold the driver lock when adjusting multicast state. - Hold the driver lock while adjusting if_capenable. PR: kern/180791 [1,2] Submitted by: Shakar Klein @ Mellanox [1,2] MFC after: 3 days
* [fixup] add Makefile changes that should have been committed in r253772avg2013-07-291-0/+3
| | | | | MFC after: 3 weeks X-MFC with: r253772
* dtrace disassembler: take the latest/last CDDL code from OpenSolarisavg2013-07-294-388/+3680
| | | | | | | | | | | OpenSolaris version is: 13108:33bb8a0301ab 6762020 Disassembly support for Intel Advanced Vector Extensions (AVX) This corresponds to Illumos-gate (github) version ab47273fedff893c8ae22ec39ffc666d4fa6fc8b MFC after: 3 weeks
* Fix a possible NULL-pointer dereference on the pfsync(4) reconfiguration.ae2013-07-291-1/+4
| | | | Reported by: Eugene M. Zheganin
* Explicitely include <machine/pcb.h>, so that we get the definition ofcognet2013-07-291-0/+1
| | | | | | | struct pcb. Submitted by: Zbyszek Bodek <zbb@semihalf.com> Pointy hat to: cognet
* Include stdint.h to fix build.ae2013-07-291-1/+2
| | | | Pointed by: Olivier Cochard-Labbé
* Restore the longer form of the _Generic. The short form does not work in C++.theraven2013-07-291-2/+11
|
* Reenable the isnan(double) / isinf(double) declarations when targeting C89 + ↵theraven2013-07-291-0/+15
| | | | SUSv2 mode.
* Define KDB_STOPPEDPCB, so that we can access the backtraces of threads runningcognet2013-07-292-0/+5
| | | | on other cores.
* Fix a debugging hack that snuck in.rpaulo2013-07-291-3/+1
|
* Firmware module for the upcoming rsu(4) driver.rpaulo2013-07-293-0/+28
|
* Realtek's RTL8712 firmware blob needed by the upcoming rsu(4) driver.rpaulo2013-07-291-0/+2149
|
* Fix alignment of USB WLAN radiotap headers. This makes USB WLAN adaptershselasky2013-07-298-16/+16
| | | | | | | work on ARM, MIPS and similar platforms, where alignment matters. MFC after: 1 week Reported by: XiaoQI Ge <ghw@7axu.com>
* Use the streaming functions for reading/writing the BAP fields on wi(4). Thisjhibbits2013-07-291-10/+4
| | | | | | | | fixes wi(4) device access on big endian architectures. PR: kern/164499 Reviewed by: adrian Obtained from: NetBSD
* Fix detection of arm ABIsbapt2013-07-281-5/+17
| | | | | Submitted by: andrew Obtained from: pkg git
* Partially close race between calls of orphan() method from GEOM and close()mav2013-07-281-0/+3
| | | | | method from ZFS core, that reliably causes use-after-free panic if SSD vdev detached during inititial erase.
* sin6 should be assigned before the loop.hrs2013-07-281-1/+1
|
OpenPOWER on IntegriCloud