ƒ·O230670 149 258 240 240 818 818 265 265 372 372 105 255 255 189 133 133 663 362 2376 2376 148 362 1218 302 125 125 224 224 172 172 145 145 144 144 130 130 365 365 170 170 1620 1630 175 175 547 540 228 160 415 128 259 259 152 322 187 187 600 128 135 192 192 437 437 235 235 125 125 305 305 456 456 463 463 265 265 2788 248 197 197 205 213 327 238 202 327 3551 206 314 206 187 327 420 130 420 407 407 203 184 303 114 133 133 181 181 181 161 277 342 139 355 182 464 248 517 144 183 385 178 195 231 149 114 471 278 822 143 327 513 513 1228 483 237 713 241 481 132 133 137 152 167 301 214 345 376 348 272 266 221 266 203 K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:16:49.163277Z K 7 svn:log V 162 MFC: r225887 Use the extended integer condition code when comparing 64-bit values. Given that ATOMIC_INC_LONG currently is unused this happened to not be fatal. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:17:58.505269Z K 7 svn:log V 144 MFC: r225888 Add a comment about why contrary to what once would think running all of userland with total store order actually is appropriate. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:18:02.111765Z K 7 svn:log V 144 MFC: r225888 Add a comment about why contrary to what once would think running all of userland with total store order actually is appropriate. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:24:03.018638Z K 7 svn:log V 722 MFC: r225889, r228222 In total store which we use for running the kernel and all of the userland atomic operations behave as if they were followed by a CPU memory barrier so there's no need to include ones in the acquire variants of atomic(9) and it's sufficient to just use include compiler memory barriers to satisfy the requirements of atomic(9). Removing the CPU memory barriers results in a small performance improvement, specifically this is sufficient to compensate the performance loss seen in the worldstone benchmark seen when using SCHED_ULE instead of SCHED_4BSD. This change is inspired by Linux even more radically doing the equivalent thing some time ago. Thanks go to Peter Jeremy for additional testing. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:24:08.305460Z K 7 svn:log V 722 MFC: r225889, r228222 In total store which we use for running the kernel and all of the userland atomic operations behave as if they were followed by a CPU memory barrier so there's no need to include ones in the acquire variants of atomic(9) and it's sufficient to just use include compiler memory barriers to satisfy the requirements of atomic(9). Removing the CPU memory barriers results in a small performance improvement, specifically this is sufficient to compensate the performance loss seen in the worldstone benchmark seen when using SCHED_ULE instead of SCHED_4BSD. This change is inspired by Linux even more radically doing the equivalent thing some time ago. Thanks go to Peter Jeremy for additional testing. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:25:28.939599Z K 7 svn:log V 169 MFC: r225890 - Add protective parentheses to macros as far as possible. - Move {r,w,}mb() to the top of this file where they live on most of the other architectures. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:25:31.542911Z K 7 svn:log V 169 MFC: r225890 - Add protective parentheses to macros as far as possible. - Move {r,w,}mb() to the top of this file where they live on most of the other architectures. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:26:50.703492Z K 7 svn:log V 276 MFC: r225891 Re-reading the Schizo errata suggests that it's actually tolerable to also use the streaming buffer of pre version 5/revision 2.3 hardware as long as we stay away from context flushes (which iommu(4) so far doesn't take advantage of). OpenSolaris does the same. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:26:55.864463Z K 7 svn:log V 276 MFC: r225891 Re-reading the Schizo errata suggests that it's actually tolerable to also use the streaming buffer of pre version 5/revision 2.3 hardware as long as we stay away from context flushes (which iommu(4) so far doesn't take advantage of). OpenSolaris does the same. END K 10 svn:author V 5 kmacy K 8 svn:date V 27 2012-01-28T23:30:39.227031Z K 7 svn:log V 11 update .Dd END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:33:50.715462Z K 7 svn:log V 159 MFC: r225899 Also allocate space for the PIL counters. Given that no machine actually uses IV_MAX interrupt vectors this wasn't a problem in practice though. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:33:53.439854Z K 7 svn:log V 159 MFC: r225899 Also allocate space for the PIL counters. Given that no machine actually uses IV_MAX interrupt vectors this wasn't a problem in practice though. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:35:24.229283Z K 7 svn:log V 94 MFC: r225900 Nuke SUN4U #ifdef's which with the demise of sun4v no longer serve any purpose. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:37:04.974518Z K 7 svn:log V 38 MFC: r225901 Remove obsolete macros. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:37:05.560661Z K 7 svn:log V 38 MFC: r225901 Remove obsolete macros. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:45:31.787081Z K 7 svn:log V 567 MFC: r206451, r206453 Add sbbc(4), a driver for the BootBus controller found in Serengeti and StarCat systems which provides time-of-day services for both as well as console service for Serengeti, i.e. Sun Fire V1280. While the latter is described with a device type of serial in the OFW device tree, it isn't actually an UART. Nevertheless the console service is handled by uart(4) as this allowed to re-use quite a bit of MD and MI code. Actually, this idea is stolen from Linux which interfaces the sun4v hypervisor console with the Linux counterpart of uart(4). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:46:36.702795Z K 7 svn:log V 266 MFC: r203845 Add ssm(4), which serves as a glue device allowing devices beneath the scalable shared memory node, which is used in large UltraSPARC III based machines to group snooping-coherency domains together, like schizo(4) to be treated like nexus(4) children. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-28T23:53:06.862347Z K 7 svn:log V 2279 MFC: r225931, r225932, r227000 Make sparc64 compatible with NEW_PCIB and enable it: - Implement bus_adjust_resource() methods as far as necessary and in non-PCI bridge drivers as far as feasible without rototilling them. - As NEW_PCIB does a layering violation by activating resources at layers above pci(4) without previously bubbling up their allocation there, move the assignment of bus tags and handles from the bus_alloc_resource() to the bus_activate_resource() methods like at least the other NEW_PCIB enabled architectures do. This is somewhat unfortunate as previously sparc64 (ab)used resource activation to indicate whether SYS_RES_MEMORY resources should be mapped into KVA, which is only necessary if their going to be accessed via the pointer returned from rman_get_virtual() but not for bus_space(9) as the later always uses physical access on sparc64. Besides wasting KVA if we always map in SYS_RES_MEMORY resources, a driver also may deliberately not map them in if the firmware already has done so, possibly in a special way. So in order to still allow a driver to decide whether a SYS_RES_MEMORY resource should be mapped into KVA we let it indicate that by calling bus_space_map(9) with BUS_SPACE_MAP_LINEAR as actually documented in the bus_space(9) page. This is implemented by allocating a separate bus tag per SYS_RES_MEMORY resource and passing the resource via the previously unused bus tag cookie so we later on can call rman_set_virtual() in sparc64_bus_mem_map(). As a side effect this now also allows to actually indicate that a SYS_RES_MEMORY resource should be mapped in as cacheable and/or read-only via BUS_SPACE_MAP_CACHEABLE and BUS_SPACE_MAP_READONLY respectively. - Do some minor cleanup like taking advantage of rman_init_from_resource(), factor out the common part of bus tag allocation into a newly added sparc64_alloc_bus_tag(), hook up some missing newbus methods and replace some homegrown versions with the generic counterparts etc. - While at it, let apb_attach() (which can't use the generic NEW_PCIB code as APB bridges just don't have the base and limit registers implemented) regarding the config space registers cached in pcib_softc and the SYSCTL reporting nodes set up. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:00:15.762604Z K 7 svn:log V 2279 MFC: r225931, r225932, r227000 Make sparc64 compatible with NEW_PCIB and enable it: - Implement bus_adjust_resource() methods as far as necessary and in non-PCI bridge drivers as far as feasible without rototilling them. - As NEW_PCIB does a layering violation by activating resources at layers above pci(4) without previously bubbling up their allocation there, move the assignment of bus tags and handles from the bus_alloc_resource() to the bus_activate_resource() methods like at least the other NEW_PCIB enabled architectures do. This is somewhat unfortunate as previously sparc64 (ab)used resource activation to indicate whether SYS_RES_MEMORY resources should be mapped into KVA, which is only necessary if their going to be accessed via the pointer returned from rman_get_virtual() but not for bus_space(9) as the later always uses physical access on sparc64. Besides wasting KVA if we always map in SYS_RES_MEMORY resources, a driver also may deliberately not map them in if the firmware already has done so, possibly in a special way. So in order to still allow a driver to decide whether a SYS_RES_MEMORY resource should be mapped into KVA we let it indicate that by calling bus_space_map(9) with BUS_SPACE_MAP_LINEAR as actually documented in the bus_space(9) page. This is implemented by allocating a separate bus tag per SYS_RES_MEMORY resource and passing the resource via the previously unused bus tag cookie so we later on can call rman_set_virtual() in sparc64_bus_mem_map(). As a side effect this now also allows to actually indicate that a SYS_RES_MEMORY resource should be mapped in as cacheable and/or read-only via BUS_SPACE_MAP_CACHEABLE and BUS_SPACE_MAP_READONLY respectively. - Do some minor cleanup like taking advantage of rman_init_from_resource(), factor out the common part of bus tag allocation into a newly added sparc64_alloc_bus_tag(), hook up some missing newbus methods and replace some homegrown versions with the generic counterparts etc. - While at it, let apb_attach() (which can't use the generic NEW_PCIB code as APB bridges just don't have the base and limit registers implemented) regarding the config space registers cached in pcib_softc and the SYSCTL reporting nodes set up. END K 10 svn:author V 5 kmacy K 8 svn:date V 27 2012-01-29T00:19:19.844015Z K 7 svn:log V 54 always exclude data bufs regardless of debug settings END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:24:46.611682Z K 7 svn:log V 266 MFC: r226054 - Use atomic operations rather than sched_lock for safely assigning pm_active and pc_pmap for SMP. This is key to allowing adding support for SCHED_ULE. Thanks go to Peter Jeremy for additional testing. - Add support for SCHED_ULE to cpu_switch(). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:32:37.384442Z K 7 svn:log V 1121 MFC: r226057 - Currently, sched_balance_pair() may cause a CPU to send an IPI_PREEMPT to itself, which sparc64 hardware doesn't support. One way to solve this would be to directly call sched_preempt() instead of issuing a self-IPI. However, quoting jhb@: "On the other hand, you can probably just skip the IPI entirely if we are going to send it to the current CPU. Presumably, once this routine finishes, the current CPU will exit softlock (or will do so "soon") and will then pick the next thread to run based on the adjustments made in this routine, so there's no need to IPI the CPU running this routine anyway. I think this is the better solution. Right now what is probably happening on other platforms is as soon as this routine finishes the CPU processes its self-IPI and causes mi_switch() which will just switch back to the softclock thread it is already running." - With r226054 (MFC'ed to stable/9 in r230690) and the the above change in place, sparc64 now no longer is incompatible with ULE and vice versa. However, powerpc/E500 still is. Submitted by: jhb Reviewed by: jeff END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:34:19.212638Z K 7 svn:log V 206 MFC: r226118 Sync with ahc(4)/ahd(4)/sym(4) etc: Zero any sense not transferred by the device as the SCSI specification mandates that any untransferred data should be assumed to be zero. Reviewed by: ken END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:35:22.451910Z K 7 svn:log V 30 MFC: r226171 Sprinkle const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:35:22.944200Z K 7 svn:log V 30 MFC: r226171 Sprinkle const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:40:39.280516Z K 7 svn:log V 128 MFC: r226175 In device_get_children() avoid malloc(0) in order to increase portability to other operating systems. PR: 154287 END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:41:08.424189Z K 7 svn:log V 128 MFC: r226175 In device_get_children() avoid malloc(0) in order to increase portability to other operating systems. PR: 154287 END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:42:54.113441Z K 7 svn:log V 77 MFC: r226270 - Remove unused remnants of MII bitbang'ing. - Sprinkle const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:42:54.772833Z K 7 svn:log V 77 MFC: r226270 - Remove unused remnants of MII bitbang'ing. - Sprinkle const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:45:52.095883Z K 7 svn:log V 50 MFC: r226948 Remove unnecessary DMA constraints. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:45:54.836981Z K 7 svn:log V 50 MFC: r226948 Remove unnecessary DMA constraints. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:47:11.578696Z K 7 svn:log V 49 MFC: r226950 Add multiple inclusion protection. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:47:14.198225Z K 7 svn:log V 49 MFC: r226950 Add multiple inclusion protection. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:49:12.526606Z K 7 svn:log V 35 MFC: r227043 Sprinkle some const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:49:14.485445Z K 7 svn:log V 35 MFC: r227043 Sprinkle some const. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:50:41.320720Z K 7 svn:log V 269 MFC: r227685 - There's no need to ignore the return value of mii_attach(9) when attaching dcphy(4) (CID 9283). - In dc_detach(), check whether ifp is NULL as dc_attach() may call the former without ifp being allocated (CID 4288). Found with: Coverity Prevent(tm) END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:50:50.432527Z K 7 svn:log V 269 MFC: r227685 - There's no need to ignore the return value of mii_attach(9) when attaching dcphy(4) (CID 9283). - In dc_detach(), check whether ifp is NULL as dc_attach() may call the former without ifp being allocated (CID 4288). Found with: Coverity Prevent(tm) END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:52:04.751189Z K 7 svn:log V 75 MFC: r227686 There's no need to read DC_10BTSTAT twice in dcphy_status(). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T00:52:07.895856Z K 7 svn:log V 75 MFC: r227686 There's no need to read DC_10BTSTAT twice in dcphy_status(). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:00:11.005652Z K 7 svn:log V 1523 MFC: r227687, r228290 - Add a hint.miibus.X.phymask hint, allowing do individually exclude PHY addresses from being probed and attaching something including ukphy(4) to it. This is mainly necessarily for PHY switches that create duplicate or fake PHYs on the bus that can corrupt the PHY state when accessed or simply cause problems when ukphy(4) isolates the additional instances. - Change miibus(4) to be a hinted bus, allowing to add child devices via hints and to set their attach arguments (including for automatically probed PHYs). This is mainly needed for PHY switches that violate IEEE 802.3 and don't even implement the basic register set so we can't probe them automatically. However, the ability to alter the attach arguments for automatically probed PHYs is also useful as for example it allows to test (or tell a user to test) new variant of a PHY with a specific driver by letting an existing driver attach to it via manipulating the IDs without the need to touch the source code or to limit a Gigabit Ethernet PHY to only announce up to Fast Ethernet in order to save energy by limiting the capability mask. Generally, a driver has to be hinted via hint.phydrv.X.at="miibusY" and hint.phydrv.X.phyno="Z" (which already is sufficient to add phydrvX at miibusY at PHY address Z). Then optionally the following attach arguments additionally can be configured: hint.phydrv.X.id1 hint.phydrv.X.id2 hint.phydrv.X.capmask - Some minor cleanup. Reviewed by: adrian, ray END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:00:16.381508Z K 7 svn:log V 1533 MFC: r227687, r228290 (partial) - Add a hint.miibus.X.phymask hint, allowing do individually exclude PHY addresses from being probed and attaching something including ukphy(4) to it. This is mainly necessarily for PHY switches that create duplicate or fake PHYs on the bus that can corrupt the PHY state when accessed or simply cause problems when ukphy(4) isolates the additional instances. - Change miibus(4) to be a hinted bus, allowing to add child devices via hints and to set their attach arguments (including for automatically probed PHYs). This is mainly needed for PHY switches that violate IEEE 802.3 and don't even implement the basic register set so we can't probe them automatically. However, the ability to alter the attach arguments for automatically probed PHYs is also useful as for example it allows to test (or tell a user to test) new variant of a PHY with a specific driver by letting an existing driver attach to it via manipulating the IDs without the need to touch the source code or to limit a Gigabit Ethernet PHY to only announce up to Fast Ethernet in order to save energy by limiting the capability mask. Generally, a driver has to be hinted via hint.phydrv.X.at="miibusY" and hint.phydrv.X.phyno="Z" (which already is sufficient to add phydrvX at miibusY at PHY address Z). Then optionally the following attach arguments additionally can be configured: hint.phydrv.X.id1 hint.phydrv.X.id2 hint.phydrv.X.capmask - Some minor cleanup. Reviewed by: adrian, ray END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:01:32.633473Z K 7 svn:log V 80 MFC: r227688 There's no need export the device interface methods of miibus(4). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:01:35.196257Z K 7 svn:log V 80 MFC: r227688 There's no need export the device interface methods of miibus(4). END K 10 svn:author V 8 rmacklem K 8 svn:date V 27 2012-01-29T01:01:41.747433Z K 7 svn:log V 449 Try and fix the NFSv4.1 client so that it performs server crash recovery correctly. Mainly required the addition of NFSERR_BADSESSION to the NFSv4.0 errors (NFSERR_STALECLIENTID, NFSERR_STALESTATEID) that indicate recovery is required. Also needed to re-initialize the session slot fields and an extra argument to nfsrpc_setclient(), so that it doesn't do a RECLAIM_COMPLETE for the recovery case. Tested minimally against the Linux NFSv4.1 server. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:22:48.128135Z K 7 svn:log V 444 MFC: r227843 (partial) - There's no need to overwrite the default device method with the default one. Interestingly, these are actually the default for quite some time (bus_generic_driver_added(9) since r52045 and bus_generic_print_child(9) since r52045) but even recently added device drivers do this unnecessarily. Discussed with: jhb, marcel - While at it, use DEVMETHOD_END. Discussed with: jhb - Also while at it, use __FBSDID. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:27:39.299205Z K 7 svn:log V 132 MFC: r226173, r227848 s,KOBJMETHOD_END,DEVMETHOD_END,g in order to fully hide the explicit mention of kobj(9) from device drivers. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:29:31.221935Z K 7 svn:log V 65 MFC: r227906 Sync with NetBSD rev. 1.104 Obtained from: NetBSD END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:32:24.898313Z K 7 svn:log V 319 MFC: r227907, r22791 (for diff reduction) Add BCM5785 but wrap it in #ifdef notyet for now. According to yongari@ there are issues probably needing workarounds in bge(4) when brgphy(4) handles this PHY. Letting ukphy(4) handle it instead results in a working configuration, although likely with performance penalties. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:35:14.937070Z K 7 svn:log V 33 MFC: r227908 Use DEVMETHOD_END. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:40:37.857652Z K 7 svn:log V 163 MFC: r227912 - Just use cam_calc_geometry(9) on newer version of FreeBSD rather than duplicating it. - In hptmv(4) and hptrr(4) use __FBSDID and DEVMETHOD_END. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T01:40:39.739592Z K 7 svn:log V 163 MFC: r227912 - Just use cam_calc_geometry(9) on newer version of FreeBSD rather than duplicating it. - In hptmv(4) and hptrr(4) use __FBSDID and DEVMETHOD_END. END K 10 svn:author V 8 rmacklem K 8 svn:date V 27 2012-01-29T01:50:26.686829Z K 7 svn:log V 55 Add the rest of the NFSv4.1 error codes to nfsproto.h. END K 10 svn:author V 6 andrew K 8 svn:date V 27 2012-01-29T02:13:01.982650Z K 7 svn:log V 226 Fix a warning where a left shift is greater than the width of an unsigned type in __glibcxx_{min,max}. The code is unused because __glibcxx_signed is false. __glibcxx_max came from libstdc++ r138078, the last GPLv2 revision. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-29T04:42:19.926330Z K 7 svn:log V 95 MFC r230460: Clarify the implementation-defined behaviour in case of close(2) returning error. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-29T04:44:52.881230Z K 7 svn:log V 95 MFC r230460: Clarify the implementation-defined behaviour in case of close(2) returning error. END K 10 svn:author V 8 mckusick K 8 svn:date V 27 2012-01-29T08:03:45.160356Z K 7 svn:log V 502 MFC r230249: Make sure all intermediate variables holding mount flags (mnt_flag) and that all internal kernel calls passing mount flags are declared as uint64_t so that flags in the top 32-bits are not lost. MFC r230250: There are several bugs/hangs when trying to take a snapshot on a UFS/FFS filesystem running with journaled soft updates. Until these problems have been tracked down, return ENOTSUPP when an attempt is made to take a snapshot on a filesystem running with journaled soft updates. END K 10 svn:author V 3 hrs K 8 svn:date V 27 2012-01-29T08:33:34.551052Z K 7 svn:log V 36 Perform IPv6 DAD only in ifn_start. END K 10 svn:author V 4 nyan K 8 svn:date V 27 2012-01-29T09:12:34.018006Z K 7 svn:log V 42 Fix build when RELEASE_CRUNCH is defined. END K 10 svn:author V 8 dumbbell K 8 svn:date V 27 2012-01-29T10:55:19.733986Z K 7 svn:log V 95 MFC r229002: Set svn:executable on dhclient-script Sponsored by: Yakaz (http://www.yakaz.com) END K 10 svn:author V 8 dumbbell K 8 svn:date V 27 2012-01-29T11:00:00.378173Z K 7 svn:log V 95 MFC r229002: Set svn:executable on dhclient-script Sponsored by: Yakaz (http://www.yakaz.com) END K 10 svn:author V 2 mm K 8 svn:date V 27 2012-01-29T12:25:21.772157Z K 7 svn:log V 345 MFC r230449: Merge illumos revisions 13540, 13562: illumos rev 13540 [1]: Removal of pyzfs broke delegation for volumes illumos rev 13562 [2]: zfs allow arguments not parsed correctly after pyzfs removal References: https://www.illumos.org/issues/1726 [1] https://www.illumos.org/issues/1977 [2] Obtained from: illumos (issues #1726, #1977) END K 10 svn:author V 2 mm K 8 svn:date V 27 2012-01-29T12:26:09.496936Z K 7 svn:log V 345 MFC r230449: Merge illumos revisions 13540, 13562: illumos rev 13540 [1]: Removal of pyzfs broke delegation for volumes illumos rev 13562 [2]: zfs allow arguments not parsed correctly after pyzfs removal References: https://www.illumos.org/issues/1726 [1] https://www.illumos.org/issues/1977 [2] Obtained from: illumos (issues #1726, #1977) END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:49:43.049922Z K 7 svn:log V 139 MFC: r228005 Change another instance of amd(4) to esp(4) missed in r227006 (MFC'ed to stable/8 in r227306). Submitted by: Garrett Cooper END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:50:43.511993Z K 7 svn:log V 139 MFC: r228005 Change another instance of amd(4) to esp(4) missed in r227006 (MFC'ed to stable/9 in r227305). Submitted by: Garrett Cooper END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:52:34.166451Z K 7 svn:log V 30 MFC: r228024 Update comment. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:52:36.212201Z K 7 svn:log V 30 MFC: r228024 Update comment. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:54:31.066922Z K 7 svn:log V 209 MFC: r228027 Move the scsi_da_bios_params() prototype from pc98_machdep.h to md_var.h where the prototype for pc98_ata_disk_firmware_geom_adjust() also lives in order to avoid an #ifdef'ed include in cam(4). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:54:36.654947Z K 7 svn:log V 209 MFC: r228027 Move the scsi_da_bios_params() prototype from pc98_machdep.h to md_var.h where the prototype for pc98_ata_disk_firmware_geom_adjust() also lives in order to avoid an #ifdef'ed include in cam(4). END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:56:18.428848Z K 7 svn:log V 360 MFC: r228209 - In device_probe_child(9) check the return value of device_set_driver(9) when actually setting a driver as especially ENOMEM is fatal in these cases. - Annotate other calls to device_set_devclass(9) and device_set_driver(9) without the return value being checked and that are okay to fail. Reviewed by: yongari (slightly earlier version) END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:56:21.025156Z K 7 svn:log V 360 MFC: r228209 - In device_probe_child(9) check the return value of device_set_driver(9) when actually setting a driver as especially ENOMEM is fatal in these cases. - Annotate other calls to device_set_devclass(9) and device_set_driver(9) without the return value being checked and that are okay to fail. Reviewed by: yongari (slightly earlier version) END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:58:06.454239Z K 7 svn:log V 367 MFC: r228211 It doesn't make much sense to check whether child is NULL after already having dereferenced it. We either should generally check the device_t's supplied to bus functions before using them (which we seem to virtually never do) or just assume that they are not NULL. While at it make this code fit 78 columns. Found with: Coverity Prevent(tm) CID: 4230 END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T12:58:07.377637Z K 7 svn:log V 367 MFC: r228211 It doesn't make much sense to check whether child is NULL after already having dereferenced it. We either should generally check the device_t's supplied to bus functions before using them (which we seem to virtually never do) or just assume that they are not NULL. While at it make this code fit 78 columns. Found with: Coverity Prevent(tm) CID: 4230 END K 10 svn:author V 6 eadler K 8 svn:date V 27 2012-01-29T14:52:42.222562Z K 7 svn:log V 169 GS105v3 exhibit the same behavior PR: docs/135999 Submitted by: Boris Kochergin No objection from: jfv Approved by: cperciva MFC after: 3 days END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T14:55:20.697905Z K 7 svn:log V 169 MFC: r228857 On FreeBSD just use the MD5 implementation of libmd rather than that of libcrypto so we don't need to relinquish csup when world is built without OpenSSL. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T14:55:38.263929Z K 7 svn:log V 2691 o MFC: r204556, r204628 Move csup away from contrib/ and into usr.bin/. Software is no longer contributed, and main development is happening in the FreeBSD repo. o MFC: r204558 Unmark authentication support as a TODO item. o MFC: r204629 Remove unused include path. o MFC: r204639 Include CURDIR in case the makefile is not run from the same directory. o MFC: r204664 Fix spelling. o MFC: r206621 Add and expand $FreeBSD$ keyword to allow committing to this file. o MFC: r206622 (partial) mdoc: order prologue macros consistently by Dd/Dt/Os Although groff_mdoc(7) gives another impression, this is the ordering most widely used and also required by mdocml/mandoc. o MFC: r208291 (partial) mdoc: consistently spell our email addresses o MFC: r210874 Don't point users at the old csup homepage. o MFC: r213300 If an RCS file is truncated, rcsfile_getdelta() will return NULL. Instead of faulting, check for NULL. However, returning an error would cause csup to just abort the entire update. Instead, break out of the loop and return ok. The attempts to update the file will trigger a MD5 failure which will cause csup to download the entire file as a fixup. o MFC: r213573 (partial) mdoc: drop redundant .Pp and .LP calls They have no effect when coming in pairs, or before .Bl/.Bd o MFC: r216370 (partial) Remove the advertising clause from UCB copyrighted files in usr.bin. This is in accordance with the information provided at ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change Also add $FreeBSD$ to a few files to keep svn happy. o MFC: r216542 Signal that data should not be modified. o MFC: r217858 Remove dead code. o MFC: r225535 Fix csup to allow case insensitive server names in the auth file, just as advertised in the manpage. PR: 158652 o MFC: r225536 Fix typos in error messages. o MFC: r225979 Update the comment to reflect what is actually going on. o MFC: r225980 Handle the situation where fixups_close() has been called but more fixups are still available on the queue. o MFC: r228625 In usr.bin/csup/auth.c, use the correct number of bytes for zeroing the shared secret, and use long long format to snprintf a time_t. o MFC: r228626 In usr.bin/csup/proto.c, use the correct printf length modifier to print an off_t. o MFC: r228667 In usr.bin/csup/auth.c, cast time_t to intmax_t instead, and use the corresponding printf length modifier. o MFC: r228857 On FreeBSD just use the MD5 implementation of libmd rather than that of libcrypto so we don't need to relinquish csup when world is built without OpenSSL. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T14:58:54.119647Z K 7 svn:log V 152 MFC: r204556 Move csup away from contrib/ and into usr.bin/. Software is no longer contributed, and main development is happening in the FreeBSD repo. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T15:00:31.127790Z K 7 svn:log V 101 MFC: r228858 Update a comment to reflect reality and explain why we're using the medany code model. END K 10 svn:author V 6 marius K 8 svn:date V 27 2012-01-29T15:00:31.949150Z K 7 svn:log V 101 MFC: r204556 Update a comment to reflect reality and explain why we're using the medany code model. END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-01-29T16:11:25.606523Z K 7 svn:log V 108 Make an assertion stronger and improve the printout for easier bug catching when it is not possible to dump END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-01-29T16:29:06.086694Z K 7 svn:log V 116 Fix format string for the pindex members as they should be treated as uintmax_t for compatibility among 32/64 bits. END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-01-29T16:44:21.497732Z K 7 svn:log V 230 Fix a bug in vm_radix_leaf() where the shifting start address can wrap-up at some point. This bug is triggered very easilly by indirect blocks in UFS which grow negative resulting in very high counts. In collabouration with: flo END K 10 svn:author V 8 jhibbits K 8 svn:date V 27 2012-01-29T18:54:25.588930Z K 7 svn:log V 140 MFC r226449: Add support for special keys (volume/brightness/eject) on Apple laptops with ADB keyboards. Approved by: nwhitehorn (mentor) END K 10 svn:author V 6 adrian K 8 svn:date V 27 2012-01-29T19:35:40.231581Z K 7 svn:log V 106 Missing code for receiving MESH PREP that should be part of r230409. Submitted by: END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-29T20:39:42.691519Z K 7 svn:log V 230 Always return 0 if the sysctl failed. This fixes the bug: when procstat -xa was run and the sysctl for a process returned ESRCH or EPERM, for this process procstat output the result collected for the previous successful process. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-29T21:08:24.438343Z K 7 svn:log V 3453 MFC r227833, r227834, r227836, r227874, r227955, r228029, r228030, r228046, r228264, r228288, r228302, r228648, r228666, r230145, r230470, r230550: New kern.proc sysctls. r227833, r227874: Add new sysctls, KERN_PROC_ENV and KERN_PROC_AUXV, to return environment strings and ELF auxiliary vectors from a process stack. Make sysctl_kern_proc_args to read not cached arguments from the process stack. Export proc_getargv() and proc_getenvv() so they can be reused by procfs and linprocfs. Suggested by: kib Reviewed by: kib Discussed with: kib, rwatson, jilles Tested by: pho MFC r227834: In procfs_doproccmdline() if arguments are not cashed read them from the process stack. Suggested by: kib Reviewed by: kib Tested by: pho MFC r227836: Retire linprocfs_doargv(). Instead use new functions, proc_getargv() and proc_getenvv(), which were implemented using linprocfs_doargv() as a reference. Suggested by: kib Reviewed by: kib Approved by: des (linprocfs maintainer) r227955: Add sysctl to get process resource limits. Reviewed by: kib r228029: In sysctl_kern_proc_auxv the process was released too early: we still need to hold it when checking process sv_flags. r228030, r228046: Add sysctl to retrieve ps_strings structure location of another process. Suggested by: kib Reviewed by: kib r228264: In sysctl_kern_proc_ps_strings() there is no much sense in checking for P_WEXIT and P_SYSTEM flags. Reviewed by: kib r228288, r228302: Protect kern.proc.auxv and kern.proc.ps_strings sysctls with p_candebug(). Citing jilles: If we are ever going to do ASLR, the AUXV information tells an attacker where the stack, executable and RTLD are located, which defeats much of the point of randomizing the addresses in the first place. Given that the AUXV information seems to be used by debuggers only anyway, I think it would be good to move it to p_candebug() now. The full virtual memory maps (KERN_PROC_VMMAP, procstat -v) are already under p_candebug(). Suggested by: jilles Discussed with: rwatson r228648: On start most of sysctl_kern_proc functions use the same pattern: locate a process calling pfind() and do some additional checks like p_candebug(). To reduce this code duplication a new function pget() is introduced and used. As the function may be useful not only in kern_proc.c it is in the kernel name space. Suggested by: kib Reviewed by: kib r228666: Fix style and white spaces. MFC r230145: Abrogate nchr argument in proc_getargv() and proc_getenvv(): we always want to read strings completely to know the actual size. As a side effect it fixes the issue with kern.proc.args and kern.proc.env sysctls, which didn't return the size of available data when calling sysctl(3) with the NULL argument for oldp. Note, in get_ps_strings(), which does actual work for proc_getargv() and proc_getenvv(), we still have a safety limit on the size of data read in case of a corrupted procces stack. Suggested by: kib r230470: Change kern.proc.rlimit sysctl to: - retrive only one, specified limit for a process, not the whole array, as it was previously (the sysctl has been added recently and has not been backported to stable yet, so this change is ok); - allow to set a resource limit for another process. Submitted by: Andrey Zonov Discussed with: kib Reviewed by: kib r230550: Fix CTL flags in the declarations of KERN_PROC_ENV, AUXV and PS_STRINGS sysctls: they are read only. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-29T21:13:36.133909Z K 7 svn:log V 109 MFC r228268: Protect process environment variables with p_candebug(). Discussed with: jilles, kib, rwatson END K 10 svn:author V 3 alc K 8 svn:date V 27 2012-01-29T21:44:25.686221Z K 7 svn:log V 221 Welcome Davide Italiano (davide) as a src committer. Davide has been working on improvements to our hardware performance monitoring and virtual memory systems. Davide will be mentored by gnn@ and me. Approved by: core END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-29T21:58:18.200932Z K 7 svn:log V 109 MFC r228268: Protect process environment variables with p_candebug(). Discussed with: jilles, kib, rwatson END K 10 svn:author V 2 mm K 8 svn:date V 27 2012-01-29T22:12:48.976302Z K 7 svn:log V 96 Update to vendor revision 4183 Obtained from: http://libarchive.googlecode.com/svn/release/2.8 END K 10 svn:author V 2 mm K 8 svn:date V 27 2012-01-29T22:20:28.383364Z K 7 svn:log V 235 Uupdate code to vendor rev. 4183 (release/2.8) Fixes vendor issue 224: "Mishandling CD9660 images with RockRidge extensions from FreeBSD makefs" References: http://code.google.com/p/libarchive/issues/detail?id=224 MFC after: 1 week END K 10 svn:author V 8 mckusick K 8 svn:date V 27 2012-01-29T23:04:29.494701Z K 7 svn:log V 322 MFC r230101: Convert FFS mount error messages from kernel printf's to using the vfs_mount_error error message facility provided by the nmount interface. Clean up formatting of mount warnings which still need to use kernel printf's since they do not return errors. Requested by: Craig Rodrigues END K 10 svn:author V 8 rmacklem K 8 svn:date V 27 2012-01-30T00:27:02.547174Z K 7 svn:log V 33 Merge in an up to date head/sys. END K 10 svn:author V 8 mckusick K 8 svn:date V 27 2012-01-30T05:45:11.676833Z K 7 svn:log V 322 MFC r230101: Convert FFS mount error messages from kernel printf's to using the vfs_mount_error error message facility provided by the nmount interface. Clean up formatting of mount warnings which still need to use kernel printf's since they do not return errors. Requested by: Craig Rodrigues END K 10 svn:author V 8 truckman K 8 svn:date V 27 2012-01-30T07:20:52.359581Z K 7 svn:log V 309 MFC r230064: Allow an MBR primary or extended Linux swap partition to be specified as the system dump device. This was already allowed for GPT. The Linux swap metadata at the beginning of the partition should not be disturbed because the crash dump is written at the end. Reviewed by: alfred, pjd, marcel END K 10 svn:author V 8 truckman K 8 svn:date V 27 2012-01-30T07:23:53.126990Z K 7 svn:log V 309 MFC r230064: Allow an MBR primary or extended Linux swap partition to be specified as the system dump device. This was already allowed for GPT. The Linux swap metadata at the beginning of the partition should not be disturbed because the crash dump is written at the end. Reviewed by: alfred, pjd, marcel END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T07:51:52.143212Z K 7 svn:log V 110 Synchronize the struct sigcontext definitions on x86 with mcontext_t. Pointed out by: bde MFC after: 1 month END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T07:53:33.634177Z K 7 svn:log V 92 Move xrstor/xsave/xsetbv into fpu.c and reorder them. Requested by: bde MFC after: 1 month END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T07:56:00.002026Z K 7 svn:log V 210 Finally, try to enable the nxstacks on amd64 and powerpc64 for both 64bit and 32bit ABIs. Also try to enable nxstacks for PAE/i386 when supported, and some variants of powerpc32. MFC after: 2 months (if ever) END K 10 svn:author V 3 mav K 8 svn:date V 27 2012-01-30T09:59:33.258522Z K 7 svn:log V 22 Fix typo in comments. END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-30T12:10:37.049366Z K 7 svn:log V 37 MFC r230531: Remove unused variable. END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-30T12:13:50.997335Z K 7 svn:log V 37 MFC r230531: Remove unused variable. END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-30T12:28:22.317146Z K 7 svn:log V 85 MFC r230613: Remove a left-over reference to make.conf(5) for now-defunct -DVM_STACK END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-30T12:29:51.575158Z K 7 svn:log V 85 MFC r230613: Remove a left-over reference to make.conf(5) for now-defunct -DVM_STACK END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-30T12:32:22.339871Z K 7 svn:log V 85 MFC r230613: Remove a left-over reference to make.conf(5) for now-defunct -DVM_STACK END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-01-30T15:09:03.816427Z K 7 svn:log V 69 Add a constant for the PCI-e surprise link down uncorrectable error. END K 10 svn:author V 3 jfv K 8 svn:date V 27 2012-01-30T16:42:02.623947Z K 7 svn:log V 184 New hardware support: Intel X540 adapter support added. Some shared code reorganization along with the new adapter. Sync changes to OACTIVE in igb into this driver. Misc small fixes. END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2012-01-30T17:17:31.602107Z K 7 svn:log V 241 Allow up to 2^24 IRQs on xics PICs, as the spec requires. Also use multipass to make sure xics is registered first so that the interrupt layer knows to expect potentially very large IRQ numbers. Some more rototilling is in order here later. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-01-30T18:28:56.758239Z K 7 svn:log V 46 Naturally align a newly added wakeup_fpusave. END K 10 svn:author V 8 ambrisko K 8 svn:date V 27 2012-01-30T19:19:22.478454Z K 7 svn:log V 257 When detaching an AIO or LIO requests grab the lock and tell knlist_remove that we have the lock now. This cleans up a locking panic ASSERT when knlist_empty is called without a lock when INVARIANTS etc. are turned. Reviewed by: kib jhb MFC after: 1 week END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T19:31:17.539683Z K 7 svn:log V 90 Fix build for the case of powerpc64 kernel without COMPAT_FREEBSD32. MFC after: 2 months END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-30T19:32:33.607679Z K 7 svn:log V 367 MFC r227839, r230146: r227839: Now kvm_getenvv() and kvm_getargv() don't need procfs(5). r230146: In kvm_argv(), the case when the supplied buffer was too short to hold the requested value was handled incorrectly, and the function retuned NULL instead of the truncated result. Fix this and also remove unnecessary check for buf != NULL, which alway retuns true. END K 10 svn:author V 7 trociny K 8 svn:date V 27 2012-01-30T19:34:41.161118Z K 7 svn:log V 151 MFC r227840, r227846: r227840: No need in procfs(5). r227846 Remove yet another outdated note about procfs(5) being required. Spotted by: arundel END K 10 svn:author V 3 jhb K 8 svn:date V 27 2012-01-30T19:35:15.956049Z K 7 svn:log V 424 Refine the implementation of POSIX_FADV_NOREUSE for the read(2) case such that instead of using direct I/O it allows read-ahead similar to POSIX_FADV_NORMAL, but invokes VOP_ADVISE(POSIX_FADV_DONTNEED) after the read(2) has completed to purge just-read data. The write(2) path continues to use direct I/O for POSIX_FADV_NOREUSE for now. Note that NOREUSE works optimally if an application reads and writes full fs blocks. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T19:50:13.480750Z K 7 svn:log V 52 Add definition for PT_GNU_RELRO. MFC after: 3 days END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T19:52:17.344237Z K 7 svn:log V 91 Add support for GNU RELRO. Submitted by: John Marino MFC after: 2 weeks END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-30T20:00:29.212661Z K 7 svn:log V 292 A debugger which requested PT_FOLLOW_FORK should get the notification about new child not only when doing PT_TO_SCX, but also for PT_CONTINUE. If TDB_FORK flag is set, always issue a stop, the same as is done for TDB_EXEC. Reported by: Dmitry Mikulin MFC after: 1 week END K 10 svn:author V 3 imp K 8 svn:date V 27 2012-01-30T20:19:28.452842Z K 7 svn:log V 86 Allow specification of build shell for the buildenv target. Submitted by: ian lepore END K 10 svn:author V 8 brueffer K 8 svn:date V 27 2012-01-30T21:02:25.114307Z K 7 svn:log V 98 Manpages for the buf_ring and drbr interfaces. Submitted by: kmacy (aeons ago) MFC after: 1 week END K 10 svn:author V 8 jhibbits K 8 svn:date V 27 2012-01-30T22:32:54.588424Z K 7 svn:log V 133 MFC r228270,228277: Add a devd notification for closing/opening the lid on PowerBooks and iBooks. Approved by: nwhitehorn (mentor) END K 10 svn:author V 3 imp K 8 svn:date V 27 2012-01-30T22:47:02.961440Z K 7 svn:log V 57 Improve media status reporting, when the driver knows... END K 10 svn:author V 3 jfv K 8 svn:date V 27 2012-01-30T23:03:21.911519Z K 7 svn:log V 22 Wrap the bool typedef END K 10 svn:author V 6 adrian K 8 svn:date V 27 2012-01-30T23:07:27.189675Z K 7 svn:log V 375 Radar API related fixes. * For legacy NICs, the combined RSSI should be used. For earlier AR5416 NICs, use control chain 0 RSSI rather than combined RSSI. For AR5416 > version 2.1, use the combined RSSI again. * Add in a missing AR5212 HAL method (get11nextbusy) which may be called by radar code. This serves no functional change for what's currently in FreeBSD. END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-01-30T23:37:17.134137Z K 7 svn:log V 179 Fix ATAPI code path to ensure bus_dma_segment structures are only used within bus_dmamap_load context. Sponsored by: Intel Reported by: Sohaib Ahsan END K 10 svn:author V 6 adrian K 8 svn:date V 27 2012-01-31T00:03:49.327970Z K 7 svn:log V 726 Add a DFS debugging mode which is useful when doing automated DFS compliance testing. In order to allow for radar pattern matching to occur, the DFS CAC/NOL handling needs to be made configurable. This commit introduces a new sysctl, "net.wlan.dfs_debug", which controls which DFS debug mode net80211 is in. * 0 = default, CSA/NOL handling as per normal. * 1 = announce a CSA, but don't add the channel to the non-occupy list (NOL.) * 2 = disable both CSA and NOL - only print that a radar event occured. This code is not compiled/enabled by default as it breaks regulatory handling. A user must enable IEEE80211_DFS_DEBUG in their kernel configuration file for this option to become available. Obtained from: Atheros END K 10 svn:author V 9 jimharris K 8 svn:date V 27 2012-01-31T00:12:51.897649Z K 7 svn:log V 45 Rebase user/jimharris/isci branch from head. END K 10 svn:author V 4 jkim K 8 svn:date V 27 2012-01-31T00:32:37.422185Z K 7 svn:log V 233 Allow contents of multiple directories to be merged to the current image. Note this patch was submitted to NetBSD and they already adopted it. http://mail-index.netbsd.org/source-changes/2012/01/28/msg031078.html MFC after: 1 week END K 10 svn:author V 5 dougb K 8 svn:date V 27 2012-01-31T00:49:04.963498Z K 7 svn:log V 418 MFC r217071 and r217213: Make the setting of the BIND CFLAG -DWORDS_BIGENDIAN conditional on the TARGET_ENDIANNESS knob from bsd.endian.mk so that we can avoid having to special-case each arch. MFC r224093 (in part): Stop claiming that we support atomic ops except on arches where we know that they work. Many users have reported problems on the other arches, so until they can get fixed we'll take the safe route. END K 10 svn:author V 5 dougb K 8 svn:date V 27 2012-01-31T00:49:34.093412Z K 7 svn:log V 418 MFC r217071 and r217213: Make the setting of the BIND CFLAG -DWORDS_BIGENDIAN conditional on the TARGET_ENDIANNESS knob from bsd.endian.mk so that we can avoid having to special-case each arch. MFC r224093 (in part): Stop claiming that we support atomic ops except on arches where we know that they work. Many users have reported problems on the other arches, so until they can get fixed we'll take the safe route. END K 10 svn:author V 6 wblock K 8 svn:date V 27 2012-01-31T01:43:03.973839Z K 7 svn:log V 1131 MFC r217314 (ae): Fix up the grammar. MFC r217342 (maxim): o Typo fixes. MFC r217343 (maxim): o Start each sentence on a new line. No content changes. MFC r222359 (ae): Add example how to create MBR and BSD schemes and install boot code. MFC r222495 (ae): Document kern.geom.part.check_integrity sysctl variable. MFC r222599 (uqs): mdoc: fix markup MFC r222646 (ru): Generally clean up markup. MFC r222778 (gavin): Rework parts of this man page to improve grammar. MFC r225003 (ae): Add new section "BOOTSTRAPPING" to the gpart(8), that describes bootstrap code images used to boot from MBR, GPT, BSD and VTOC8 schemes. MFC r227774: Add a section that explicitly describes partitioning schemes. Modify existing sections to refer to the new one. Rearrange partitioning scheme list so MBR and EBR types are together. Also add several corrections for grammar, clarity, and consistency. MFC r227777: Fix date. MFC r227800: Correct and expand BSD partitioning scheme description. Correct GUID to GPT in RECOVERING section. MFC r229838: Clarity improvements. MFC r229847: Whitespace-only fix. Approved by: gjb (mentor) END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-01-31T01:45:20.082264Z K 7 svn:log V 386 MFC r227758,227759,227788: Introduce macro stubs in the mutex and sxlock implementation that will be always defined and will allow consumers, willing to provide options, file and line to locking requests, to not worry about options redefining the interfaces. This is typically useful when there is the need to build another locking interface on top of the mutex one. Requested by: kib END K 10 svn:author V 7 attilio K 8 svn:date V 27 2012-01-31T01:51:30.303217Z K 7 svn:log V 140 MFC r227814: - Use ppb_assert_locked() rather than using explicit mtx_assert call - Make ppbus code agnostic in regard of INVARIANTS option END K 10 svn:author V 8 rmacklem K 8 svn:date V 27 2012-01-31T02:11:05.092955Z K 7 svn:log V 615 jwd@ reported a problem via email to freebsd-fs@ on Aug 25, 2011 under the subject "F_RDLCK lock to FreeBSD NFS fails to R/O target file". This occurred because the server side NLM always checked for VWRITE access, irrespective of the type of lock request. This patch replaces VOP_ACCESS(..VWRITE..) with one appropriate to the lock operation. It allows unlock and lock cancellation to be done without a check of VOP_ACCESS(), so that files can't be left locked indefinitely after the file permissions have been changed. Discussed with: zack Submitted by: jwd (earlier version) Reviewed by: dfr MFC after: 2 weeks END K 10 svn:author V 8 jhibbits K 8 svn:date V 27 2012-01-31T02:30:47.232422Z K 7 svn:log V 143 MFC r230640: Remove the notify match from a couple devd apple events, the events don't include notify tags. Approved by: nwhitehorn (mentor) END K 10 svn:author V 8 rmacklem K 8 svn:date V 27 2012-01-31T03:58:26.500093Z K 7 svn:log V 383 When a "mount -u" switches an NFS mount point from TCP to UDP, any thread doing an I/O RPC with a transfer size greater than NFS_UDPMAXDATA will be hung indefinitely, retrying the RPC. After a discussion on freebsd-fs@, I decided to add a warning message for this case, as suggested by Jeremy Chadwick. Suggested by: freebsd at jdc.parodius.com (Jeremy Chadwick) MFC after: 2 weeks END K 10 svn:author V 5 kevlo K 8 svn:date V 27 2012-01-31T05:49:49.835006Z K 7 svn:log V 38 Fix a whitespace nit Reviewed by: bz END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-31T10:46:51.260050Z K 7 svn:log V 37 MFC r230531: Remove unused variable. END K 10 svn:author V 3 kib K 8 svn:date V 27 2012-01-31T11:00:33.963710Z K 7 svn:log V 45 MFC r227698: Update the manpage for r227697. END K 10 svn:author V 3 mav K 8 svn:date V 27 2012-01-31T12:57:21.802139Z K 7 svn:log V 60 Just in case, clear stream interrupts before enabling them. END K 10 svn:author V 7 pluknet K 8 svn:date V 27 2012-01-31T13:00:40.091239Z K 7 svn:log V 71 Isolate v_caddr_t in the ie driver. Submitted by: Bruce Evans on net@ END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:19:02.908538Z K 7 svn:log V 207 pj4b: Fix data corruption in WB mode pj4b_idcache_wbinv_range function cleaned and invalidated wrong data range, thus causing data corruption. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:23:45.946731Z K 7 svn:log V 120 Remove unnecessary clean and invalidate cache operations Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:25:00.537814Z K 7 svn:log V 251 armadaxp: Fix generation of mask for coherency fabric initialization Mask was set for wrong number of cores (one less than real number), thus causing problems with proper initialization. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 6 emaste K 8 svn:date V 27 2012-01-31T15:32:05.025626Z K 7 svn:log V 280 Add -e to set arbitrary kernel environment variables. Nextboot(8) can now set any combination of kernel name (-k), kernel options (-o), and environment strings (-e). As a result of this change -k also becomes optional. Reviewed by: freebsd-current (Ian Lepore, pluknet@, jhb@) END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:36:21.572276Z K 7 svn:log V 254 Change AP cores startup procedure Cores were initialized and started one-by-one, thus causing problems with coherency fabric initialization. Now all AP cores are started at the same moment. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:38:06.082503Z K 7 svn:log V 178 Fix TTB setup When multiprocessor system is used, shareable flag must be set when TTB is stored in CP15 register. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:39:06.558766Z K 7 svn:log V 172 armv7: Fix TTB setup, little cleanup When TTB is written to CP15 register, proper memory model must be set. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:40:18.187753Z K 7 svn:log V 127 pj4b: Add workaround for hangup after releasing AP's in WT mode Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:41:31.705194Z K 7 svn:log V 172 Add flag shared to page table Page table may be used by more than one processor,so flag shared must be set. Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END K 10 svn:author V 4 gber K 8 svn:date V 27 2012-01-31T15:45:10.918715Z K 7 svn:log V 109 pj4b: Add memory barriers to cache operations Submitted by: Lukasz Plachno Obtained from: Marvell, Semihalf END