summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MFC r320052:kib2017-06-241-21/+25
| | | | Do not leak syslog_mutex on cancellation.
* MFC r320183: Reduce code duplication in rpc.lockd.delphij2017-06-241-195/+76
| | | | | | | | | | Reuse create_service code instead of duplicating it in lookup_addresses for kernel NLM. As a (good) side effect this also fixed a few issues that were already fixed in the former but never applied to the latter. Reviewed by: kevlo
* MFC r320038:kib2017-06-231-7/+8
| | | | Style.
* Revert r320228 as wellngie2017-06-221-3/+3
| | | | See r320229 for the other related revert commit.
* Revert r320222,r320223,r320224ngie2017-06-2226-349/+108
| | | | | | | The committed changes (reverted after this commit) break POLA on a stable branch. Requested by: jhb
* MFC r318545:ngie2017-06-221-5/+3
| | | | | | | | | | | | | | Install {cron.d,newsyslog.conf.d,syslog.d} via `make distribution`, not `make install` I incorrectly started this pattern in r277541 with the opensm newsyslog.conf.d file, and continued using it in r318441 and r318443. This will fix the files being handled improperly via installworld, preventing tools like etcupdate, mergemaster, etc from functioning properly when comparing the installed contents on a system vs the contents in a source tree when doing merges. PR: 219404 MFC with: r277541, r318441, r318443
* MFC r309194,r309216:ngie2017-06-221-0/+1
| | | | | | | | | | | | | r309194 (by bapt): initialize *nextp which could be left uninitialized in case the configuration file cannot be open/read CID: 1365665 r309216 (by bapt): Properly initialize nextp
* MFC r308158:ngie2017-06-221-2/+3
| | | | | | | r308158 (by bapt): Allow symlinks to be followed in cron.d directories and fix detection of regular files on NFS
* MFC r308139,r308157,r308160,r316818,r318250,r318443:ngie2017-06-2227-108/+349
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r308139 (by bapt): cron(8): add support for /etc/cron.d and /usr/local/etc/cron.d For automation tools it is way easier to maintain files in directories rather than modifying /etc/crontab. The files in those directories are in the same format as /etc/crontab Relnotes: yes r308157 (by bapt): Fix typo in cron(8) date r308160 (by bapt): syslogd(8): add an 'include' keyword All the '.conf' files not beginning with a '.' contained int he directory following the keyword will be included. This keyword can only be used in the first level configuration files. Modify the default syslogd.conf to 'include' /etc/syslog.d and /usr/local/etc/syslog.d It simplify a lot handling of syslog from automation tools. Relnotes: yes r316818: Conditionally install /etc/pam.d/ftp* and /etc/pam.d/telnetd /etc/pam.d/ftp* should be installed with MK_FTP != no and /etc/pam.d/telnetd should be installed when MK_TELNET != no. r318250: Handle the logfiles in newsyslog and syslogd conditionally, based on src.conf(5) knobs This will allow consumers of FreeBSD to use the unmodified configuration files out of the box more than previously. Both newsyslog.conf and syslog.conf: - /var/log/lpd-errs (MK_LPR != no) - /var/log/ppp.log (MK_PPP != no) - /var/log/xferlog (MK_FTP != no) newsyslog.conf: - /var/log/amd.log (MK_AMD != no) - /var/log/pflog (MK_PF != no) - /var/log/sendmail.st (MK_SENDMAIL != no) r318443: Conditionally handle the crontab entry for atrun(8) The default crontab prior to this commit assumes atrun(8) is always present, which isn't true if MK_AT == no. Move atrun(8) execution from /etc/crontab to /etc/cron.d/at, and base /etc/cron.d/at's installation on MK_AT. cron(8) will detect /etc/cron.d/at's presence when the configuration is loaded and run atrun every 5 minutes like it would prior to this commit. SHELL and PATH are duplicated between /etc/crontab and /etc/cron.d/at because atrun(8) executes programs, which may rely on environment set in the current default /etc/crontab. Noted by: bdrewery (in an internal review) Relnotes: yes (may need to add environmental modifications to /etc/cron.d/at)
* MFC 313186, 319702: Account for overhead of page structures when sizing page ↵jhb2017-06-211-43/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | array. 313186: Over the years, the code and comments in vm_page_startup() have diverged in one respect. When determining how many page structures to allocate, contrary to what the comments say, the code does not account for the overhead of a page structure per page of physical memory. This revision changes the code to match the comments. 319702: Fix an off-by-one error in the VM page array on some systems. r313186 changed how the size of the VM page array was calculated to be less wasteful. For most systems, the amount of memory is divided by the overhead required by each page (a page of data plus a struct vm_page) to determine the maximum number of available pages. However, if the remainder for the first non-available page was at least a page of data (so that the only memory missing was a struct vm_page), this last page was left in phys_avail[] but was not allocated an entry in the VM page array. Handle this case by explicitly excluding the page from phys_avail[]. Requested by: alc
* The GEOM KPI in stable/10 requires Giant to be unacquired (a requirementmarius2017-06-201-0/+3
| | | | | | | dropped in r300287). So wrap calling into GEOM in {DROP,PICKUP}_GIANT(), similar to what as been done prio to r300288. This fixes a "Giant owned" panic with r318159 in place and INVARIANTS enabled. Reported by: Oliver Pinter
* MFC r319964davidcs2017-06-2076-59909/+65201
| | | | | | Upgrade STORMFW to 8.30.0.0 and ecore version to 8.30.0.0 Add support for pci deviceID 0x8070 for QLE41xxx product line which supports 10GbE/25GbE/40GbE
* MFC r319932:markj2017-06-201-22/+40
| | | | Fix handling of subpage BIO_WRITE and BIO_DELETE requests on swap MDs.
* MFC 319490: Remove stale cap_rights_get(2) manpage.jhb2017-06-202-1/+2
| | | | | | | | The documentation moved to section 3 several years ago, but 'man cap_rights_get' pulls up cap_rights_limit(2) (which is MLINKed to cap_rights_get.2) instead of cap_rights_get(3). Approved by: re (gjb)
* MFC r319916:kib2017-06-201-1/+0
| | | | Remove stray return.
* MFC r279833: Use the correct event table for Haswell Xeon eventsavg2017-06-201-1/+1
|
* Direct commit to stable/10 to correctly setting the EIAC and IMSsbruno2017-06-191-1/+1
| | | | | | | | | registers to the same values when processing interrupts. This resolves PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 PR: 211219 Submitted by: Franco Fitchner <franco@opnsense.org>
* MFC r318867: fix vmxnet3 crash when LRO is enabledavg2017-06-191-0/+14
| | | | Sponsored by: Panzura
* MFC r311224: Fix PMC architecture check to handle later IPAs including Skylakeavg2017-06-191-1/+1
|
* MFC r292070: More fixes in the various intel processors, fixing missingavg2017-06-191-76/+75
| | | | IAP_F_FM's...
* MFC r291494: Add support for Intel Skylake and Intel Broadwell PMC's.avg2017-06-195-257/+1085
|
* MFC r281101: Remove whitespace [in hwpmc]avg2017-06-191-9/+9
|
* MFC r279939: hwpmc: Fix event number to match enum nameavg2017-06-191-2/+2
|
* MFC r279836: Add missing counter definitionsavg2017-06-191-1/+6
|
* MFC r279835: Fix Ivy Bridge+ MEM_UOPS_RETIRED countersavg2017-06-196-154/+110
|
* MFC r279834: Support architectural events on Haswell/Ivy Bridgeavg2017-06-191-0/+4
|
* MFC r279832: Fix Sandy Bridge+ hwpmc branch countersavg2017-06-198-450/+364
|
* MFC r279829: Add manpage for Haswell Xeon pmc implementationavg2017-06-192-0/+976
|
* MFC r279831: Fix pmc unit restrictions to match documentationavg2017-06-191-2/+2
|
* MFC r279830: Fix various bugs in Haswell counter definitionsavg2017-06-191-6/+6
|
* MFC r277524: style(9) cleanup in hwpmcavg2017-06-193-16/+27
|
* MFC 281102: hwpmc: add initial Intel Broadwell support.avg2017-06-194-1/+25
|
* MFC r319962:cy2017-06-191-1/+1
| | | | | | Correct example directory location. Submitted by: olivier@
* MFC r319676:pfg2017-06-181-2/+4
| | | | | | | | patch: if reading fails, do not go into infinite loop asking for a filename. This can happen if no tty is available. Obtained from: OpenBSD (CVS rev 1.54)
* MFC r319972:hselasky2017-06-181-2/+2
| | | | | | | | | Use static device numbering instead of dynamic one when creating mlx4en network interfaces. This prevents infinite unit number growth typically when the mlx4en driver is used inside virtual machines which support runtime PCI attach and detach. Sponsored by: Mellanox Technologies
* MFC 319670jpaetzel2017-06-151-0/+4
| | | | | | | Fix SMBFS when saved passwords are greater than 18 characters PR: 132302 Submitted by: dhorn2000@gmail.com guru@unixarea.de
* MFC r319954:gjb2017-06-151-6/+6
| | | | | | | Modernize FreeBSD version numbers in freebsd-update(8). While here, expand a contraction to make textproc/igor happy. Sponsored by: The FreeBSD Foundation
* MFC r319852:delphij2017-06-151-4/+3
| | | | | | | | | | Fix buffer lengths. After r319369, the RPC code validates caller supplied buffer length in taddr2uaddr. When no -h is specified, the sizeof(ai_addr) is used, which is always smaller than the required size and therefore uaddr would be NULL, causing the kernel to copyin() from userland NULL and fail with EFAULT.
* MFC r318995alc2017-06-153-40/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In r118390, the swap pager's approach to striping swap allocation over multiple devices was changed. However, swapoff_one() was not fully and correctly converted. In particular, with r118390's introduction of a per- device blist, the maximum swap block size, "dmmax", became irrelevant to swapoff_one()'s operation. Moreover, swapoff_one() was performing out-of- range operations on the per-device blist that were silently ignored by blist_fill(). This change corrects both of these problems with swapoff_one(), which will allow us to potentially increase MAX_PAGEOUT_CLUSTER. Previously, swapoff_one() would panic inside of blist_fill() if you increased MAX_PAGEOUT_CLUSTER. MFC r319001 After r118390, the variable "dmmax" was neither the correct strip size nor the correct maximum block size. Moreover, after r318995, it serves no purpose except to provide information to user space through a read- sysctl. This change eliminates the variable "dmmax" but retains the sysctl. It also corrects the value returned by the sysctl. MFC r319604 Halve the memory being internally allocated by the blist allocator. In short, half of the memory that is allocated to implement the radix tree is wasted because we did not change "u_daddr_t" to be a 64-bit unsigned int when we changed "daddr_t" to be a 64-bit (signed) int. (See r96849 and r96851.) MFC r319612 When the function blist_fill() was added to the kernel in r107913, the swap pager used a different scheme for striping the allocation of swap space across multiple devices. And, although blist_fill() was intended to support fill operations with large counts, the old striping scheme never performed a fill larger than the stripe size. Consequently, the misplacement of a sanity check in blst_meta_fill() went undetected. Now, moving forward in time to r118390, a new scheme for striping was introduced that maintained a blist allocator per device, but as noted in r318995, swapoff_one() was not fully and correctly converted to the new scheme. This change completes what was started in r318995 by fixing the underlying bug in blst_meta_fill() that stops swapoff_one() from simply performing a single blist_fill() operation. MFC r319627 Starting in r118390, swaponsomething() began to reserve the blocks at the beginning of a swap area for a disk label. However, neither r118390 nor r118544, which increased the reservation from one to two blocks, correctly accounted for these blocks when updating the variable "swap_pager_avail". This change corrects that error. MFC r319655 Originally, this file could be compiled as a user-space application for testing purposes. However, over the years, various changes to the kernel have broken this feature. This revision applies some fixes to get user- space compilation working again. There are no changes in this revision to code that is used by the kernel.
* MFC: 319690dexuan2017-06-141-0/+2
| | | | | | | | | | | | | | r319690 hyperv/pcib: use the device serial number as PCI domain Currently the PCI domain is initialized with the instance GUID in vmbus_pcib_attach(). It turns out the GUID can change across VM reboot, while some users want a persistent value for PCI domain. The solution is that we can change to use the device serial number, which starts with 1 and is unique within a VM. Obtained from: Haiyang Zhang Sponsored by: Microsoft
* MFC r313021, r319621:gjb2017-06-081-2/+2
| | | | | | | | | | | | r313021 (brd): Force a few variables to be uppercase when they are evaluated. r319621: Ensure ${_CW} is uppercase when passing '-c' to mk-vmimage.sh, otherwise with 'CLOUDWARE=vagrant-virtualbox', the path to the configuration file may be incorrect. Sponsored by: The FreeBSD Foundation
* MFC r318780:kib2017-06-072-26/+26
| | | | Use __BSD_VISIBLE test instead checking for absense of _POSIX_SOURCE.
* MFC r318781:kib2017-06-071-0/+30
| | | | Add BIT_OR2(), BIT_AND2(), BIT_NAND2(), BIT_XOR() and BIT_XOR2().
* MFC r318998:cy2017-06-061-2/+2
| | | | | | | Fix return value of ip_sync_nat. Previously, regardless of error it always returned a return code of 0. Obtained from: NetBSD ip_sync.c r1.5
* Work around a gcc 4.2 bug on powerpc architectures, where usingdim2017-06-061-2/+7
| | | | | | | | | | | | -fdata-sections can cause bogus "section type conflict" errors. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33168 for more information. Since the upstream fixes are under GPLv3 and non-trivial, just disable using function and data sections, at the cost of a slightly larger executable. Direct commit to stable/10, since the version of clang in head and stable/11 cannot be built by gcc 4.2 at all.
* MFC r318943 (avg):gjb2017-06-061-0/+3
| | | | | | | | | | | | | | | | | | | | | | MFV r318942: 8166 zpool scrub thinks it repaired offline device https://www.illumos.org/issues/8166 If we do a scrub while a leaf device is offline (via "zpool offline"), we will inadvertently clear the DTL (dirty time log) of the offline device, even though it is still damaged. When the device comes back online, we will incompletely resilver it, thinking that the scrub repaired blocks written before the scrub was started. The incomplete resilver can lead to data loss if there is a subsequent failure of a different leaf device. The fix is to never clear the DTL of offline devices. Note that if a device is onlined while a scrub is in progress, the scrub will be restarted. The problem can be worked around by running "zpool scrub" after "zpool online". See also https://github.com/zfsonlinux/zfs/issues/5806 PR: 219537 Sponsored by: The FreeBSD Foundation
* MFC r319369:delphij2017-06-069-30/+96
| | | | | | | | | | | | | * limit size of buffers to RPC_MAXDATASIZE * don't leak memory * be more picky about bad parameters From: https://raw.githubusercontent.com/guidovranken/rpcbomb/master/libtirpc_patch.txt https://github.com/guidovranken/rpcbomb/blob/master/rpcbind_patch.txt via NetBSD.
* Document r319390, cxgbetool(8) addition.gjb2017-06-051-2/+53
| | | | | | | | | | | | | | | Document r298427, truss(1) '-H' flag. Document r304017, ptrace(2) threaded process debugging improvements. Document r306533, devctl(8) 'clear driver' added. Document r309560, cxgbe(4) T6 support. Document r309447, cxgbe(4) VF support for T4/T5 cards. Document r309560, cxgbe(4) VF support for T6 cards. Document r308154, cxgbe(4) additional virtual interface support. Document r306520, PCI passthrough/bhyve improvements. Document r306472, PCI passthrough/bhyve improvements. Submitted by: jhb Sponsored by: The FreeBSD Foundation
* MFC r319413:hselasky2017-06-041-3/+2
| | | | | | | | | Free hardware queue resource after port is stopped in the mlx4en(4) driver. Else if the port is up the resource might still be busy and the MTT free will fail. PR: 216493 Sponsored by: Mellanox Technologies
* MFC r319414:hselasky2017-06-041-30/+12
| | | | | | | | | | | | Allow communication between functions on the same host when using the mlx4en(4) driver in SRIOV mode. Place a copy of the destination MAC address in the send WQE only under SRIOV/eSwitch configuration or when the device is in selftest. This allows communication between functions on the same host. PR: 216493 Sponsored by: Mellanox Technologies
OpenPOWER on IntegriCloud