summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MFC r315031:gonzo2017-05-111-1/+1
| | | | | | | [fdt] Make DTBs generated by make_dtb.sh overlay-ready Generate symbols node when compiling dts files so they can be modified during boot-time by applying overlays.
* MFC 313407,313449: Copy ELF machine/flags from binaries to core dumps.jhb2017-05-114-16/+27
| | | | | | | | | | | | | | | | | 313407: Copy the e_machine and e_flags fields from the binary into an ELF core dump. In the kernel, cache the machine and flags fields from ELF header to use in the ELF header of a core dump. For gcore, the copy these fields over from the ELF header in the binary. This matters for platforms which encode ABI information in the flags field (such as o32 vs n32 on MIPS). 313449: Trim trailing whitespace (mostly introduced in r313407). Sponsored by: DARPA / AFRL
* MFC r317584:hselasky2017-05-111-1/+1
| | | | Correct manual page link to usbdi(9).
* MFC r317523:kib2017-05-111-0/+51
| | | | Add asserts to verify stability of struct proc and struct thread layouts.
* MFC 313999: Consolidate statements to initialize files.jhb2017-05-111-30/+26
| | | | | | | | | | | | | | Previously, the first lines of various generated files from system call tables were generated in two sections. Some of the initialization was done in BEGIN, and the rest was done when the first line was encountered. The main reason for this split before r313564 was that most of the initialization done in the second section depended on the $FreeBSD$ tag extracted from the system call table. Now that the $FreeBSD$ tag is no longer used, consolidate all of the file initialization in the BEGIN section. This change was tested by confirming that the content of generated files did not change.
* MFC 316512,316537: Use correct linker emulations for armeb and riscv.jhb2017-05-111-2/+2
|
* MFC 316493: Assert that the align parameter to uma_zcreate() is valid.jhb2017-05-111-0/+3
|
* MFC 315323: Use UMA_ALIGN_PTR instead of sizeof(void *) for zone alignment.jhb2017-05-111-1/+1
| | | | | | | uma_zcreate()'s alignment argument is supposed to be sizeof(foo) - 1, and uma.h provides a set of helper macros for common types. Passing sizeof(void *) results in all of the members being misaligned triggering unaligned access faults on certain architectures (notably MIPS).
* MFC 314894: Fix a couple of typos and reword some sentences in bsd.README.jhb2017-05-101-5/+5
|
* MFC 313564:jhb2017-05-1037-46/+14
| | | | | | | | | | | | | Drop the "created from" line from files generated by makesyscalls.sh. This information is less useful when the generated files are included in source control along with the source. If needed it can be reconstructed from the $FreeBSD$ tag in the generated file. Removing this information from the generated output permits committing the generated files along with the change to the system call master list without having inconsistent metadata in the generated files. Regenerate the affected files along with the MFC.
* MFC: r314097marius2017-05-109-129/+156
| | | | | | | | | | | | | | | - Allow different slicers for different flash types to be registered with geom_flashmap(4) and teach it about MMC for slicing enhanced user data area partitions. The FDT slicer still is the default for CFI, NAND and SPI flash on FDT-enabled platforms. - In addition to a device_t, also pass the name of the GEOM provider in question to the slicers as a single device may provide more than one provider. - Build a geom_flashmap.ko. - Use MODULE_VERSION() so other modules can depend on geom_flashmap(4). - Remove redundant/superfluous GEOM routines that either do nothing or provide/just call default GEOM (slice) functionality. - Trim/adjust includes
* MFC: r305507marius2017-05-101-1/+1
| | | | | | | | | | | | | | | | | | Disable vt(4) by default on sparc64 as creator_vt(4) and vt_ofwfb(4) have the serious problem of not actually attaching the hardware they are driving at the bus level. This causes creator(4) and machfb(4) to attach and drive the very same hardware in parallel when both syscons(4) and vt(4) as well as their associated hardware drivers are built into a kernel, i. e. GENERIC, at the same time. Also, syscons(4) and its drivers still are way superior to vt(4) and its equivalents; unlike the syscons(4) counterparts the vt(4) drivers don't provide hardware acceleration resulting in considerably slower screen drawing, creator_vt(4) doesn't provide a /dev/fb node as required by the Xorg sunffb(4) etc. In theory, vt_ofwfb(4) should be able to handle more devices than machfb(4). However, testing shows that it hardly works with any hardware machfb(4) isn't also able to drive, making vt(4) and vt_ofwfb(4) not favorable for the time being from that perspective either.
* MFC: r311817marius2017-05-101-65/+115
| | | | | | | | | | | | | | | | | | | | | In dummynet(4), random chunks of memory are casted to struct dn_*, potentially leading to fatal unaligned accesses on architectures with strict alignment requirements. This change fixes dummynet(4) as far as accesses to 64-bit members of struct dn_* are concerned, tripping up on sparc64 with accesses to 32-bit members happening to be correctly aligned there. In other words, this only fixes the tip of the iceberg; larger parts of dummynet(4) still need to be rewritten in order to properly work on all of !x86. In principle, considering the amount of code in dummynet(4) that needs this erroneous pattern corrected, an acceptable workaround would be to declare all struct dn_* packed, forcing compilers to do byte-accesses as a side-effect. However, given that the structs in question aren't laid out well either, this would break ABI/KBI. While at it, replace all existing bcopy(9) calls with memcpy(9) for performance reasons, as there is no need to check for overlap in these cases. PR: 189219
* MFC: r310712marius2017-05-103-11/+32
| | | | | | | | | | | - Use correct offsets into the keys set array. As the elements of this zero-length array are dynamically sized at run-time based on the use of hints, compilers can't be expected to figure out these offsets on their own. [1] - Fix incorrect comparison in cmp_nans(). [2] PR: 204571 [1], 202301 [2] Submitted by: David Binderman [2]
* MFC r317740:ken2017-05-104-36/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Correct loop mode CRN resets to adhere to FCP-4 section 4.10 Prior to this change, the CRN (Command Reference Number) is reset on any firmware LIP, LOOP DOWN, or LOOP RESET event in violation of FCP-4 which specifies that the CRN should only be reset in response to a LIP Reset (LIPyx) primitive. FCP-4 also indicates PLOGI/LOGO and PRLI/PRLO ELS actions as conditions for resetting the CRN for the associated initiator port. These violations manifest themselves when the HBA is removed from the loop, or a target device is removed (especially during an outstanding command) without power cycling. If the HBA and and the target device determine upon re-establishing the loop that no PLOGI or PRLI is required, and the target does not issue a LIPxy to the initiator, the CRN for the target will have been improperly reset by the isp driver. As a result, the target port will silently ignore all FCP commands issued during the device probe (which will time out) preventing the device from attaching. This change corrects thie CRN reset behavior in response to loop state changes, also introduces CRN resets for the above mentioned ELS actions as encountered through async PDB change events. This change also adds cleanup of outstanding commands in isp_loop_dead() that was previously missing. sys/dev/isp/isp.c Add the last login state to debug output when syncing the pdb sys/dev/isp/isp_freebsd.c Replace binary statement setting aborted ccb status in isp_watchdog() with the XS_SETERR macro used elsewhere In isp_loop_dead(), abort or complete pending commands as done in isp_watchdog() In isp_async(), segregate the ISPASYNC_LOOP_RESET action from ISPASYNC_LIP, ISPASYNC_LOOP_DOWN, and ISPASYNC_LOOP_UP fallthroughs, and only reset the CRN in the RESET case. Also add checks to handle false LOOP RESET actions that do not have a proper associated LIP primitive, and log the primitive in the debug messages In isp_async(), remove the goto from ISP_ASYNC_DEV_STAYED, and only reset the CRN in the DEV_CHANGED action In isp_async(), when processing an ISPASYNC_CHANGE_PDB status, reset CRN(s) for the associated nphdl (or all ports) if the change reason is some form of ELS login/logout. Also remove assignment to fc since it is not used in the scope sys/dev/isp/ispmbox.h Add macro definition for the global N-Port handle, and correct a macro typo 'PDB24XX_AE_PRLI_DONJE' sys/dev/isp/ispvar.h Add macros FCP_AL_DA_ALL, FCP_AL_PA, and FCP_IS_DEST_ALPD for more legible code when determining if an AL_PD port matches the portid for a given struct fcparam* by value or by virtue of the AL_PD port being 0xFF Submitted by: Reid Linnemann Sponsored by: Spectra Logic
* Document r308914, zfsbootcfg(8) addition.gjb2017-05-101-0/+4
| | | | Sponsored by: The FreeBSD Foundation
* MFC 313409: Defer startup of gjournal switcher kproc.jhb2017-05-101-11/+35
| | | | Don't start switcher kproc until the first GEOM is created.
* MFC r317775:ken2017-05-102-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix error recovery behavior in the pass(4) driver. After FreeBSD SVN revision 236814, the pass(4) driver changed from only doing error recovery when the CAM_PASS_ERR_RECOVER flag was set on a CCB to sometimes doing error recovery if the passed in retry count was non-zero. Error recovery would happen if two conditions were met: 1. The error recovery action was simply a retry. (Which is most cases.) 2. The retry_count is non-zero. (Which happened a lot because of cut-and-pasted code.) This explains a bug I noticed in with camcontrol: # camcontrol tur da34 -v Unit is ready # camcontrol reset da34 Reset of 1:172:0 was successful At this point, there should be a Unit Attention: # camcontrol tur da34 -v Unit is ready No Unit Attention. Try it again: # camcontrol reset da34 Reset of 1:172:0 was successful Now set the retry_count to 0 for the TUR: # camcontrol tur da34 -v -C 0 Unit is not ready (pass42:mps1:0:172:0): TEST UNIT READY. CDB: 00 00 00 00 00 00 (pass42:mps1:0:172:0): CAM status: SCSI Status Error (pass42:mps1:0:172:0): SCSI status: Check Condition (pass42:mps1:0:172:0): SCSI sense: UNIT ATTENTION asc:29,2 (SCSI bus reset occurred) (pass42:mps1:0:172:0): Field Replaceable Unit: 2 There is the unit attention. camcontrol(8) has a default retry_count of 1, in case someone sets the -E flag without setting -C. The CAM_PASS_ERR_RECOVER behavior was only broken with the CAMIOCOMMAND ioctl, which is the synchronous pass(4) API. It has worked as intended (error recovery is only done when the flag is set) in the asynchronous API (CAMIOQUEUE ioctl). sys/cam/scsi/scsi_pass.c: In passsendccb(), when calling cam_periph_runccb(), only specify the error routine when CAM_PASS_ERR_RECOVER is set. share/man/man4/pass.4: Document that CAM_PASS_ERR_RECOVER is needed to enable error recovery. Reported by: Terry Kennedy <TERRY@glaver.org> PR: kern/218572 Sponsored by: Spectra Logic
* MFC r317666:ae2017-05-101-5/+6
| | | | | | Add sets support for ipfw table info/list/flush commands. PR: 212668
* MFC r317667:ae2017-05-101-1/+1
| | | | | | | In parse_range() validate both range values instead of checking the top value twice. PR: 202295
* MFC r317663:ae2017-05-101-7/+7
| | | | | | | | Properly initialize ipfw_range_tlv variable to fix possible EINVAL in case when ipfw delete/zero/resetlog command issued for several rules in the loop. Also reorder some variables by size. PR: 218993
* MFC r317682:ae2017-05-102-9/+37
| | | | | | Add `ipfw table all destroy` support. PR: 212669
* MFC: r317465rmacklem2017-05-101-1/+10
| | | | | | | | | | Fix handling of a NFSv4.1 callback reply from the session cache. The nfsv4_seqsession() call returns NFSERR_REPLYFROMCACHE when it has a reply in the session, due to a requestor retry. The code erroneously assumed a return of 0 for this case. This patch fixes this and adds a KASSERT(). This would be an extremely rare occurrence. It was found during code inspection during the pNFS server development.
* MFC r317265:pfg2017-05-095-7/+7
| | | | | | | lib: initial use of reallocarray(3). Make some use of reallocarray, attempting to limit it to cases where the parameters are unsigned and there is some theoretical chance of overflow.
* Document SA-17:04.gjb2017-05-091-0/+7
| | | | Sponsored by: The FreeBSD Foundation
* Fix svn revision ordering.gjb2017-05-091-4/+4
| | | | Sponsored by: The FreeBSD Foundation
* MFC r310343-r310344gonzo2017-05-093-12/+22
| | | | | | | | | | | | | | | | | | | | | r310343: [iMX6] Fix build for SSI driver and add dependency for SDMA driver - Pass correct pointer to OF_getencprop - Check the size of "dmas" property - Add dependency on sdma driver Reviewed by: br Differential Revision: https://reviews.freebsd.org/D8873 r310344: [iMX6] Fix SDMA driver build - Place const modifiers where required - Make sure sdma device is attahched before consumers like SSI Reviewed by: br Differential Revision: https://reviews.freebsd.org/D8874
* Document r310009, jail_confwarn rc.conf(5) addition.gjb2017-05-092-1/+5
| | | | Sponsored by: The FreeBSD Foundation
* DIRDEPS_BUILD: Connect new directories.bdrewery2017-05-095-0/+64
| | | | | | This is a direct commit since MFCing these changes is impractical. Sponsored by: Dell EMC Isilon
* Document r308942, bytgpio(4) addition.gjb2017-05-091-0/+4
| | | | Sponsored by: The FreeBSD Foundation
* Document r307768, jedec_ts(4) addition.gjb2017-05-091-0/+6
| | | | Sponsored by: The FreeBSD Foundation
* Document r308104, chromebook_platform(4) addition.gjb2017-05-091-1/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r317116, qlnxe(4) addition.gjb2017-05-091-0/+4
| | | | Sponsored by: The FreeBSD Foundation
* Document r317182, qlxgbe(4) firmware version 5.4.64.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* DIRDEPS_BUILD: Update dependencies.bdrewery2017-05-0915-15/+9
| | | | | | This is a direct commit since MFCing these changes is impractical. Sponsored by: Dell EMC Isilon
* MFC r315009:gonzo2017-05-0934-501/+2839
| | | | | | Merge from vendor branch importing dtc 1.4.3 Major new feature in this import is FDT overlay support
* MFC r317415:bdrewery2017-05-092-2/+0
| | | | Remove an incorrect MLINK for tree(3) introduced in r310728.
* MFC r303450:bdrewery2017-05-091-3/+8
| | | | Pull a copy of the input string before calling basename() and dirname().
* MFC r306806, r313709, r317058, r317060gonzo2017-05-0913-925/+1625
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r306806 by emaste: Improvements to BSD-licensed DTC. - Numerous crash and bug fixes - Improved warning and error messages - Permit multiple labels on nodes and properties - Fix node@address references - Add support for /delete-node/ - Consume whitespace after a node - Read the next token before the second /memreserve/ - Fix parsing of whitespace - Clean up /delete-node/ and add support for /delete-property/ - Handle /delete-node/ specifying a unit address Obtained from: https://github.com/davidchisnall/dtc @df5ede4 r313709 by dim: Fix build of BSD dtc when NDEBUG is defined (MK_ASSERT_DEBUG=no): * Initialize correct parent in binary_operator's constructor. * Include <errno.h> explicitly, otherwise errno is undefined (without NDEBUG, this is accidentally 'fixed' by including <iostream>). Reported by: matteo r317058 by emaste: dtc: remove unused (since r306806) string.hh r317060 by emaste: dtc: update to upstream 227d6a3 - Report missing includes at the correct location. - Add initial support for the -@ option emitting a symbol table. - Add support for running tests with and without -@ - Add support for generating __fixups__ and __local_fixups__ - Attach the to-string transform to the node path.
* Document r307729, unbound 1.5.10.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r309511, Subversion 1.9.5.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Add missing revision.gjb2017-05-091-1/+2
| | | | Sponsored by: The FreeBSD Foundation
* Document r309847, file version 5.29.gjb2017-05-091-0/+2
| | | | Sponsored by: The FreeBSD Foundation
* Document r312517, xz version 5.2.3.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r313537, tcpdump version 4.9.0.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r313680, NetBSD test suite 01.11.2017_23.20 snapshot.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r313795, zlib 1.2.11.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r313980, openresolv version 3.9.0.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Document r314278, libucl version 20170219.gjb2017-05-091-0/+3
| | | | Sponsored by: The FreeBSD Foundation
* Fix revision number for libarchive v3.3.1.gjb2017-05-091-3/+3
| | | | Sponsored by: The FreeBSD Foundation
OpenPOWER on IntegriCloud