summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Resolve the confusion between the head_list and the hook list.andre2013-08-242-35/+48
| | | | | | | | | | | The linked list of pfil hooks is changed to "chain" and this term is applied consistently. The head_list remains with "list" term. Add KASSERT to vnet_pfil_uninit(). Update and extend comments. Reviewed by: eri (previous version)
* pfil_hook_get() has been internalized in r254771 and is no longerandre2013-08-241-9/+2
| | | | part of the API. It wasn't safe for external use in any case.
* Internalize pfil_hook_get(). There are no outside consumers ofandre2013-08-242-12/+13
| | | | | | | this API, it is only safe for internal use and even the pfil(9) man page says so in the BUGS section. Reviewed by: eri
* Convert one instance of pfil hook callback missed in r254769.andre2013-08-241-4/+1
|
* Introduce typedef for pfil hook callback function and replace allandre2013-08-242-13/+9
| | | | | | spelled out occurrences with it. Reviewed by: eri
* Revert lldb changes due to post-3.3 clang and llvm API changesemaste2013-08-246-37/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | Revisions: svn git 183929 99447a6 183862 15c1774 source/Host/common/FileSpec.cpp 184954 007e7bc 184948 4dc3761 source/Expression/ClangExpressionParser.cpp 182099 b31044e 181387 779e6ac include/lldb/Expression/IRExecutionUnit.h source/Expression/IRExecutionUnit.cpp 184177 0b2934b 182650 f2dcf35 181703 7bef4e2 source/Plugins/Disassembler/llvm/DisassemblerLLVMC.cpp 182683 0d91b80 source/Plugins/Instruction/ARM/EmulateInstructionARM.cpp Sponsored by: DARPA, AFRL
* sh: Do not prematurely discard stopped jobs in a wait builtin.jilles2013-08-241-5/+1
| | | | | | | | | | | | | If a job is specified to 'wait', wait for it to complete. Formerly, in interactive mode, the job was deleted if it stopped. If no jobs are specified in interactive mode, 'wait' still waits for all jobs to complete or stop. In non-interactive mode, WUNTRACED is not passed to wait3() so stopped jobs are not detected. PR: bin/181435
* Add new attribute lunname to report only textual LUN-specific device IDs.mav2013-08-242-5/+15
| | | | | While lunid attribute prefers to report numeric ones, having both may be useful in some situations.
* Add support to physio(9) for devices that don't want I/O split andken2013-08-245-6/+221
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configure sa(4) to request no I/O splitting by default. For tape devices, the user needs to be able to clearly understand what blocksize is actually being used when writing to a tape device. The previous behavior of physio(9) was that it would split up any I/O that was too large for the device, or too large to fit into MAXPHYS. This means that if, for instance, the user wrote a 1MB block to a tape device, and MAXPHYS was 128KB, the 1MB write would be split into 8 128K chunks. This would be done without informing the user. This has suboptimal effects, especially when trying to communicate status to the user. In the event of an error writing to a tape (e.g. physical end of tape) in the middle of a 1MB block that has been split into 8 pieces, the user could have the first two 128K pieces written successfully, the third returned with an error, and the last 5 returned with 0 bytes written. If the user is using a standard write(2) system call, all he will see is the ENOSPC error. He won't have a clue how much actually got written. (With a writev(2) system call, he should be able to determine how much got written in addition to the error.) The solution is to prevent physio(9) from splitting the I/O. The new cdev flag, SI_NOSPLIT, tells physio that the driver does not want I/O to be split beforehand. Although the sa(4) driver now enables SI_NOSPLIT by default, that can be disabled by two loader tunables for now. It will not be configurable starting in FreeBSD 11.0. kern.cam.sa.allow_io_split allows the user to configure I/O splitting for all sa(4) driver instances. kern.cam.sa.%d.allow_io_split allows the user to configure I/O splitting for a specific sa(4) instance. There are also now three sa(4) driver sysctl variables that let the users see some sa(4) driver values. kern.cam.sa.%d.allow_io_split shows whether I/O splitting is turned on. kern.cam.sa.%d.maxio shows the maximum I/O size allowed by kernel configuration parameters (e.g. MAXPHYS, DFLTPHYS) and the capabilities of the controller. kern.cam.sa.%d.cpi_maxio shows the maximum I/O size supported by the controller. Note that a better long term solution would be to implement support for chaining buffers, so that that MAXPHYS is no longer a limiting factor for I/O size to tape and disk devices. At that point, the controller and the tape drive would become the limiting factors. sys/conf.h: Add a new cdev flag, SI_NOSPLIT, that allows a driver to tell physio not to split up I/O. sys/param.h: Bump __FreeBSD_version to 1000049 for the addition of the SI_NOSPLIT cdev flag. kern_physio.c: If the SI_NOSPLIT flag is set on the cdev, return any I/O that is larger than si_iosize_max or MAXPHYS, has more than one segment, or would have to be split because of misalignment with EFBIG. (File too large). In the event of an error, print a console message to give the user a clue about what happened. scsi_sa.c: Set the SI_NOSPLIT cdev flag on the devices created for the sa(4) driver by default. Add tunables to control whether we allow I/O splitting in physio(9). Explain in the comments that allowing I/O splitting will be deprecated for the sa(4) driver in FreeBSD 11.0. Add sysctl variables to display the maximum I/O size we can do (which could be further limited by read block limits) and the maximum I/O size that the controller can do. Limit our maximum I/O size (recorded in the cdev's si_iosize_max) by MAXPHYS. This isn't strictly necessary, because physio(9) will limit it to MAXPHYS, but it will provide some clarity for the application. Record the controller's maximum I/O size reported in the Path Inquiry CCB. sa.4: Document the block size behavior, and explain that the option of allowing physio(9) to split the I/O will disappear in FreeBSD 11.0. Sponsored by: Spectra Logic
* CTL changes required for iSCSI target, most notably LUN remappingtrasz2013-08-247-64/+160
| | | | | | and a mechanism to allow CTL frontends for retrieving LUN options. Reviewed by: ken (earlier version)
* MFV r254751:delphij2013-08-241-1/+4
| | | | | | | | | | Don't treat the parameter as a number (pool GUID) when there is error converting it from string, instead, treat it as the pool name. Illumos ZFS issues: 1765 assert triggered in libzfs_import.c trying to import pool name beginning with a number
* MFV r254749:delphij2013-08-242-38/+14
| | | | | | | | | | | Don't hold dd_lock for long by breaking it when not doing dsl_dir accounting. It is not necessary to hold the lock while manipulating the parent's accounting, because there is no interface for userland to see a consistent picture of both parent and child at the same time anyway. Illumos ZFS issues: 4046 dsl_dataset_t ds_dir->dd_lock is highly contended
* Grow some spares in struct vfsops.alfred2013-08-241-0/+1
| | | | | This should hopefully prevent ABI breakage on adding new vfsops in 10.x.
* MFV r254748:delphij2013-08-241-1/+5
| | | | | | | Fix memory leak in libzfs's iter_dependents_cb(). Illumos ZFS issues: 4061 libzfs: memory leak in iter_dependents_cb()
* MFV r254747:delphij2013-08-248-89/+97
| | | | | | | | | Fix a panic from dbuf_free_range() from dmu_free_object() while doing zfs receive. This is a regression from FreeBSD r253821. Illumos ZFS issues: 4047 panic from dbuf_free_range() from dmu_free_object() while doing zfs receive
* MFV r254746:delphij2013-08-231-15/+42
| | | | | | | | | | To quote original Illumos ticket: libctf thinks that any ELF file containing more than 65536 sections is corrupt, because it doesn't understand the SHN_XINDEX magic. Illumos DTrace issues: 4005 libctf can't deal with extended sections
* Merge ACPICA 20130823.jkim2013-08-2341-105/+1070
|
* MFV r254422:delphij2013-08-235-18/+209
| | | | | | | | Illumos DTrace issues: 3089 want ::typedef 3094 libctf should support removing a dynamic type 3095 libctf does not validate arrays correctly 3096 libctf does not validate function types correctly
* Correctly remove an interface's ipv4 address when the user callsasomers2013-08-231-3/+3
| | | | | | | | | | "/etc/rc.d/netif stop XXX". The old globbing pattern failed to account for the possibility of a tab occuring before "inet". Reviewed by: will Approved by: ken (mentor, implicit) MFC after: Never (bug affects head only) Sponsored by: Spectra Logic
* Hold mfi_io_lock across calls to xpt_rescan() and xpt_alloc_ccb_nowait().markj2013-08-231-5/+1
| | | | | | | | | xpt_rescan() expects the SIM lock to be held, and we trip a mtx_assert if the driver initiates multiple rescans in quick succession. Reported by: sbruno Tested by: sbruno MFC after: 1 week
* Allow tmpfs be mounted inside jail.delphij2013-08-234-3/+26
|
* Remove duplicate copy of the man pagebryanv2013-08-231-112/+0
| | | | Pointed out by: jmallett
* Add vmx(4), a VMware VMXNET3 ethernet driver ported from OpenBSDbryanv2013-08-2310-0/+4244
|
* Return EIO iso -1, the kiic_transfer has an signed return.andreast2013-08-231-1/+1
| | | | Submitted by: Luiz Otavio O Souza <loos.br AT gmail.com>
* Assorted fixes to krping. Disconnect the rest of sys/contrib/rdma fromnp2013-08-234-11/+26
| | | | | | | | the build while here. sys/ofed has more recent RDMA code and should be used instead. We should probably move krping out of sys/contrib/rdma and get rid of the rest of it. Obtained from: Chelsio
* Fix implementation of sock_getname.np2013-08-231-5/+5
| | | | MFC after: 1 week
* Set the hint for physical address of RSDP in hexadecimal as before r223262.jkim2013-08-231-1/+1
|
* Whitespace cleanup.np2013-08-231-2/+1
|
* Merge lldb r188801 to contrib/llvm/tools/lldb/emaste2013-08-23885-0/+362847
|\
| * Import lldb as of SVN r188801emaste2013-08-23885-0/+362847
| | | | | | (A number of files not required for the FreeBSD build have been removed.) Sponsored by: DARPA, AFRL
* There is no need to hold the freelist lock around alloc/free ofnp2013-08-231-10/+1
| | | | | | | software descriptors. This also silences WITNESS warnings when the software descriptors are allocated with M_WAITOK. MFC after: 1 week
* Addendum to r254141: The call to vm_radix_insert() in vm_page_cache() canalc2013-08-233-0/+25
| | | | | | | | | | reclaim the last preexisting cached page in the object, resulting in a call to vdrop(). Detect this scenario so that the vnode's hold count is correctly maintained. Otherwise, we panic. Reported by: scottl Tested by: pho Discussed with: attilio, jeff, kib
* Fix a whitespace.jkim2013-08-231-1/+1
|
* Don't give up so easily on failure of CMD55 to put the card into app-cmdian2013-08-231-3/+3
| | | | | | mode. We don't know why it failed, so we can't know that a retry will also fail (the low-level driver might have reset the controller state machine or something similar that would allow a retry to work).
* Since the 253927, which removed the soft busy call for the sf page, itkib2013-08-231-1/+2
| | | | | | | | | | | | | does not make sense to wait for the soft busy state of the page to drain. The vm object lock is dropped immediately after, so the result of the wait is invalidated. It might make sense to not wait for the hard busy state as well, esp. for the fully valid page, but this is postponed for now. Reviewed by: alc Tested by: pho Sponsored by: The FreeBSD Foundation
* zfs: do not reject any operations on a pool just because it's a boot poolavg2013-08-231-0/+2
| | | | | | | | Unlike the upstream FreeBSD supports booting to all kinds of pools. Requested by: many Tested by: sbruno MFC after: 12 days
* fbt: drop a local write-only variableavg2013-08-231-6/+0
| | | | | Discovered with: gcc46 MFC after: 4 days
* Fix the build and fix style.davide2013-08-231-2/+2
| | | | Pointy-hat to: davide
* zfs: inline and remove zfs_vnode_lockavg2013-08-233-15/+5
| | | | | | | | It didn't serve any useful purpose, but obscured file and line information useful for debugging. MFC after: 5 days X-MFC with: r254445
* - Bump date.davide2013-08-231-2/+2
| | | | | | - Small mdoc fix. Submitted by: pluknet
* Add libexecinfo Makefileemaste2013-08-231-0/+19
| | | | Sponsored by: DARPA, AFRL
* libc: Access some unexported variables more efficiently (related to stdio).jilles2013-08-231-2/+2
|
* Introduce callout_init_rm() so that callouts can be used in conjunctiondavide2013-08-232-6/+23
| | | | | | | | | with rmlocks. This works only with non-sleepable rm because handlers run in SWI context. While here, document the new KPI in the timeout(9) manpage. Requested by: adrian, scottl Reviewed by: mav, remko(manpage)
* libc: Make various internal file descriptors from fopen() close-on-exec.jilles2013-08-2313-21/+21
|
* Use tvtohz() to convert a socket buffer timeout to a tick value ratherjhb2013-08-231-7/+2
| | | | | | | | than using a home-rolled version. The home-rolled version could result in shorter-than-requested sleeps. Reported by: Vitja Makarov <vitja.makarov@gmail.com> MFC after: 2 weeks
* Update libexecinfo man page for FreeBSDemaste2013-08-231-9/+11
| | | | Sponsored by: DARPA, AFRL
* Some vendors store the mac addresses of arge(4) as a literal sring in thesbruno2013-08-232-7/+21
| | | | | | | | | | | | | form xx:xx:xx:xx:xx:xx complete with ":" characters taking of 18 bytes instead of 6 integers. Expose a "readascii" tuneable to handle this case. Remove restriction on eepromac assignement for the first dev instance only. Add eepromac address for DIR-825 to hints file. Add readascii hint for DIR-825 Reviewed by: adrian@
* FreeBSD compatibility for libexecinfoemaste2013-08-232-0/+2
|
* Import NetBSD libexecinfo 20130822 to contribemaste2013-08-239-0/+935
|\
* | Remove accidental import of libexecinfo at wrong directory levelemaste2013-08-2318-1870/+0
| |
OpenPOWER on IntegriCloud