summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add more locale-specific functions to the relevant man pages andissyl02012-06-255-3/+46
| | | | | | | | | | Makefiles: - libc/stdtime/strftime.3 - libc/stdtime/strptime.3 - libc/stdlib/strfmon.3 Reviewed by: theraven Approved by: gabor (mentor)
* Add missing MLINKS for whatever -> if_whatever.trasz2012-06-251-0/+18
| | | | | Reviewed by: brueffer MFC after: 1 week
* Fix a LOR acquiring the if_afdata lock while holding an rtentry lock.delphij2012-06-251-18/+16
| | | | | | | | | | | | Possibly do some entra work in case we would not get into the ifa0 != NULL paths later as we already do for the mltaddr before. XXX We should possibly error in case in6_setscope fails. Reference: http://lists.freebsd.org/pipermail/freebsd-net/2011-September/029829.html Submitted by: bz MFC after: 1 week
* Unify sctp_input() and sctp6_input().tuexen2012-06-252-182/+114
| | | | MFC after: 3 days
* MFV (r237567):delphij2012-06-252-6/+9
| | | | | | | | Fetch both ECDSA and RSA keys by default in ssh-keyscan(1). Approved by: des Obtained from: OpenSSH portable MFC after: 1 week
* Handle case when result of pmap_pte is NULL. This issue was uncoveredgonzo2012-06-251-2/+4
| | | | by r237367
* Whitespace cleanup.tuexen2012-06-258-99/+99
| | | | MFC after: 3 days
* Fix clang warning when compiling iw_cxgb.np2012-06-251-1/+1
| | | | Reported by: rene, dim
* Mesh mode, potential garbage in QoS subfield.monthadar2012-06-251-3/+3
| | | | | | | | * qos[1] subfield is never assigned a value before this statement. qos[1] can potentially be OR:ed with garbage. Make it an assignment instead; * Remove brackets around if statement; Approved by: adrian
* Fix 'make depend'.uqs2012-06-252-4/+4
|
* Add PV chunk and list locking to pmap_change_wiring(), pmap_protect(), andalc2012-06-251-57/+109
| | | | | | | | pmap_remove(). The execution of these functions is no longer serialized by the pvh global lock. Make some stylistic changes to the affected code for the sake of consistency with related code elsewhere in the pmap.
* Fix size of the bcopy when extracting ethernet addresskevlo2012-06-251-1/+1
| | | | Obtained from: DragonFly
* Correct sizeof usagekevlo2012-06-256-6/+6
| | | | Obtained from: DragonFly
* Consume spare fields for the providergone pointers added to the g_class andken2012-06-251-4/+2
| | | | | | | | g_geom structures in change 237518. The original change would have broken the ABI. Suggested by: ae MFC after: 4 days
* Unbreak register tests for parallel SCSI.mjacob2012-06-251-2/+5
| | | | | You can't overwrite registers 7 and 8. MFC after: 3 days
* Pass the packet length explicitly around.tuexen2012-06-245-30/+9
| | | | MFC after: 3 days
* Remove redundant check.tuexen2012-06-241-11/+3
| | | | MFC after: 3 days
* Do packet logging in a consistent way.tuexen2012-06-246-26/+30
| | | | MFC after: 3 days
* Clean up multi-id mode so it's driven by the f/w loaded,mjacob2012-06-246-54/+100
| | | | | | | | | | | | not by some hint setting. Do more preparations for FC-Tape. Clean up resource counting for 24XX or later chipsets so we find out after EXEC_FIRMWARE what is actually supported. Set target mode exchange count based upon whether or not we are supporting simultaneous target/initiator mode. Clean up some old (pre-24XX) xfwoption and zfwoption issues. Sponsored by: Spectralogic MFC after: 3 days
* Add the sys directory we create to the list of items to clean.andrew2012-06-241-0/+1
|
* In a complete lack of foresight on my part, my previous commit brokeadrian2012-06-245-0/+6
| | | | | | | | | | | | | | | | | | | the assumption that ath_softc doesn't change size based on build time configuration. I picked up on this because suddenly radar stuff didn't work; and although the ath_dfs code was setting sc_dodfs=1, the main ath driver saw sc_dodfs=0. So for now, include opt_ath.h in driver source files. This seems like the sane thing to do anyway. I'll have to do a pass over the code at some later stage and turn the radiotap TX/RX structs into malloc'ed memory, rather than in-line inside of ath_softc. I'd rather like to keep ath_softc the same layout regardless of configuration parameters. Pointy hat to: adrian
* Create a symlink to sys/elf32.h, sys/elf64.h, and sys/elf_common.h.andrew2012-06-241-1/+15
| | | | | | | | | | | | | | | | When building libelf in the bootstrap stage this would include the tree versions of, for example, sys/_types.h. This would work as long as the tree's version of this file was close enough to the system's version of the file. If, however, there was a change in the tree such that the location of a typedef was moved this would cause problems. In this case the version of sys/_types.h in the tree no longer defines __wchar_t and expects it to to be defined in machine/_types.h, however we pick up machine/_types.h from the system and find it is not defined there. The solution is to restrict the parts of sys er include from the tree to those that are needed. This fixes the recent Tinderbox failure. Pointy Hat to: andrew
* Shuffle these initialisations to where they should be.adrian2012-06-241-7/+7
|
* Change the ath_dfs_process_phy_err() method to take an mbuf rather thanadrian2012-06-243-10/+14
| | | | | | | | a buffer pointer. For large radar pulses, the AR9130 and later will return a series of FFT results for software processing. These can overflow a single 2KB buffer on longer pulses. This would result in undefined buffer behaviour.
* Fix mandoc "Oc breaks Op" warning.joel2012-06-241-1/+1
|
* Remove the assert added in r237286eadler2012-06-241-2/+0
| | | | | | | | | The use of assertions in libraries is not widely accepted. Requested by: bde, scottl Approved by: cperciva MFC after: 3 days X-MFC-With: r237286
* Introduce an optional ath(4) radiotap vendor extension.adrian2012-06-244-2/+166
| | | | | | | | | | | | | | | | | | | | | | This includes a few new fields in each RXed frame: * per chain RX RSSI (ctl and ext); * current RX chainmask; * EVM information; * PHY error code; * basic RX status bits (CRC error, PHY error, etc). This is primarily to allow me to do some userland PHY error processing for radar and spectral scan data. However since EVM and per-chain RSSI is provided, others may find it useful for a variety of tasks. The default is to not compile in the radiotap vendor extensions, primarily because tcpdump doesn't seem to handle the particular vendor extension layout I'm using, and I'd rather not break existing code out there that may be (badly) parsing the radiotap data. Instead, add the option 'ATH_ENABLE_RADIOTAP_VENDOR_EXT' to your kernel configuration file to enable these options.
* On second thought, let's just set both CRC and PHY errors together onadrian2012-06-241-3/+6
| | | | | | frames that have it and let the upper layer sort it out. PR: kern/169362
* Sometimes the AR5416 sends back radar PHY errors with both the PHY erroradrian2012-06-241-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | and the CRC error bits set. The radar payload is correct. When this happens, the stack doesn't see them PHY error frames and isn't interpreted as a PHY error. So, no radar detection and no radiotap PHY error handling. Now, this may introduce some weird issues if the MAC sends up some other combination of CRC error + PHY error frames; this commit would break that and mark them as PHY errors instead of CRC errors. I may tinker with this a little more to pass radar/early radar/spectral frames up as PHY errors if the CRC bit is set, to restore the previous behaviour (where if CRC is set on a PHY error frame, it's marked as a CRC error rather than PHY error.) Tested on: AR5416, over the air, to a USRP N200 which is generating a large number of a variety of radar pulses. TODO: Test on AR9130, AR9160, AR9280 (and maybe radar pulses on 2GHz on AR9285/AR9287.) PR: kern/169362
* Fix a bug which causes a panic in daopen(). The panic is caused byken2012-06-248-19/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a da(4) instance going away while GEOM is still probing it. In this case, the GEOM disk class instance has been created by disk_create(), and the taste of the disk is queued in the GEOM event queue. While that event is queued, the da(4) instance goes away. When the open call comes into the da(4) driver, it dereferences the freed (but non-NULL) peripheral pointer provided by GEOM, which results in a panic. The solution is to add a callback to the GEOM disk code that is called when all of its resources are cleaned up. This is implemented inside GEOM by adding an optional callback that is called when all consumers have detached from a provider, and the provider is about to be deleted. scsi_cd.c, scsi_da.c: In the register routine for the cd(4) and da(4) routines, acquire a reference to the CAM peripheral instance just before we call disk_create(). Use the new GEOM disk d_gone() callback to register a callback (dadiskgonecb()/cddiskgonecb()) that decrements the peripheral reference count once GEOM has finished cleaning up its resources. In the cd(4) driver, clean up open and close behavior slightly. GEOM makes sure we only get one open() and one close call, so there is no need to set an open flag and decrement the reference count if we are not the first open. In the cd(4) driver, use cam_periph_release_locked() in a couple of error scenarios to avoid extra mutex calls. geom.h: Add a new, optional, providergone callback that is called when a provider is about to be deleted. geom_disk.h: Add a new d_gone() callback to the GEOM disk interface. Bump the DISK_VERSION to version 2. This probably should have been done after a couple of previous changes, especially the addition of the d_getattr() callback. geom_disk.c: Add a providergone callback for the disk class, g_disk_providergone(), that calls the user's d_gone() callback if it exists. Bump the DISK_VERSION to 2. geom_subr.c: In g_destroy_provider(), call the providergone callback if it has been provided. In g_new_geomf(), propagate the class's providergone callback to the new geom instance. blkfront.c: Callers of disk_create() are supposed to pass in DISK_VERSION, not an explicit disk API version number. Update the blkfront driver to do that. disk.9: Update the disk(9) man page to include information on the new d_gone() callback, as well as the previously added d_getattr() callback, d_descr field, and HBA PCI ID fields. MFC after: 5 days
* Make the wchar_t type machine dependent.andrew2012-06-2415-45/+40
| | | | | | | | | | | | | | This is required for ARM EABI. Section 7.1.1 of the Procedure Call for the ARM Architecture (AAPCS) defines wchar_t as either an unsigned int or an unsigned short with the former preferred. Because of this requirement we need to move the definition of __wchar_t to a machine dependent header. It also cleans up the macros defining the limits of wchar_t by defining __WCHAR_MIN and __WCHAR_MAX in the same machine dependent header then using them to define WCHAR_MIN and WCHAR_MAX respectively. Discussed with: bde
* Introduce reserve_pv_entry() and use it in pmap_pv_demote_pde(). In orderalc2012-06-231-1/+83
| | | | | | | | | to add PV list locking to pmap_pv_demote_pde(), it is necessary to change the way that pmap_pv_demote_pde() allocates PV entries. Specifically, once pmap_pv_demote_pde() begins modifying the PV lists, it can't allocate any new PV chunks, because that could require the PV list lock to be dropped. So, all necessary PV chunks must be allocated in advance. To my surprise, this new approach is a few percent faster than the old one.
* Better way to determine the status page length and rx pad boundary.np2012-06-231-12/+17
|
* Remove superfluous paragraph macro.joel2012-06-231-1/+0
|
* Add description about dev.acpi_ibm.0.handlerevents.iwasaki2012-06-231-1/+26
| | | | MFC after: 3 days
* Add in-driver event handler.iwasaki2012-06-231-86/+371
| | | | MFC after: 3 days
* Correct device id for GPU on some server SandyBridge model.kib2012-06-231-1/+1
| | | | | Submitted and tested by: Thomas Zander <thomas.e.zander googlemail com> MFC after: 3 days
* Unbreak options ZFS after r236884.marius2012-06-231-0/+4
|
* Release the ADB keyboard mutex when handling the power buttonjhibbits2012-06-231-0/+2
| | | | | | | press/release. Found by WITNESS. Approved by: nwhitehorn (mentor) MFC after: 3 days
* Fix interface matching by ipfw tablemelifaro2012-06-231-1/+2
| | | | | | | Submitted by: Ihor Kaharlichenko <madkinder@gmail.com> Tested by: Ihor Kaharlichenko <madkinder@gmail.com> Approved by: kib(mentor) MFC after: 3 days
* Add scsi_extract_sense_ccb() -- wrapper around scsi_extract_sense_len().mav2012-06-235-71/+56
| | | | It allows to remove number of duplicate checks from several places.
* Move the code dealing with shared page into a dedicatedkib2012-06-233-192/+241
| | | | | | kern_sharedpage.c source file from kern_exec.c. MFC after: 29 days
* Remove no longer needed forward declaration for struct sf_buf.kib2012-06-231-1/+0
| | | | MFC after: 29 days
* Stop updating the struct vdso_timehands from even handler executed inkib2012-06-234-101/+66
| | | | | | | | | | | | | | | | | | | | | | the scheduled task from tc_windup(). Do it directly from tc_windup in interrupt context [1]. Establish the permanent mapping of the shared page into the kernel address space, avoiding the potential need to sleep waiting for allocation of sf buffer during vdso_timehands update. As a consequence, shared_page_write_start() and shared_page_write_end() functions are not needed anymore. Guess and memorize the pointers to native host and compat32 sysentvec during initialization, to avoid the need to get shared_page_alloc_sx lock during the update. In tc_fill_vdso_timehands(), do not loop waiting for timehands generation to stabilize, since vdso_timehands is written in the same interrupt context which wrote timehands. Requested by: mav [1] MFC after: 29 days
* Do not allocate extra vectors when adapter is not TOEnp2012-06-222-8/+13
| | | | | | capable (or toecaps have been disallowed by the user). + one very minor unrelated cleanup in t4_sge.c
* Return CAM_SEL_TIMEOUT and CAM_DEV_NOT_THERE instead of CAM_TID_INVALIDmav2012-06-221-2/+2
| | | | | | | | and CAM_LUN_INVALID for case of missing devices. In removes tons of error messages from CAM during bus scans. Reported and tested by: Mike Tancsa <mike@sentex.net> MFC after: 3 days
* Just add a comment to further investigate when being closer to that codebz2012-06-221-0/+1
| | | | again next time. The condition of the 2nd if() is very unlikely ever met.
* Import Illumos revision 13736:9f1d48e1681fmm2012-06-221-0/+3
| | | | | | | | | | 2901 ZFS receive fails for exabyte sparse files References: https://www.illumos.org/issues/2901 Obtained from: illumos (issue #2901) MFC after: 1 week
* Change 'camcontrol defects' to first probe a drive to find out how muchken2012-06-223-7/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | defect information it has before grabbing the full defect list. This works around a bug with some Hitachi drives that generate data overrun errors when they are asked for more defect data than they have. The change is done in a spec-compliant way, so it should have no negative impact on drives that don't have this issue. This is based on work originally done at Sandvine. scsi_da.h: Add a define for the maximum amount of data that can be contained in a defect list. camcontrol.c: Update the readdefects() function to issue an initial command to determine the length of the defect list, and then use that length in the request for the full defect list. camcontrol.8: Add a note that some drives will report 0 defects available if you don't request either the PLIST or GLIST. Submitted by: Mark Johnston <markjdb@gmail.com> (original version) MFC after: 3 days
* - Add a comment explaining the locking of the cached pages pool heldattilio2012-06-221-1/+14
| | | | | | | | | | | | | | by vm_objects. - Add flags for the per-object lock and free pages queue mutex lock. Use the newly added flags to mark the cache root within the vm_object structure. Please note that other vm_object members should be marked with correct locking but they are left for other commits. In collabouration with: alc MFC after: 3 days3 days3 days
OpenPOWER on IntegriCloud