summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* MFC r315871: MFV r315791: ntp 4.2.8p10.delphij2017-03-28410-73539/+16529
|
* MFC r315639:ngie2017-03-271-0/+5
| | | | | | libcam: NULL out freed `ccb.cdm.matches` and `ccb.cdm.patterns` pointers This is being done to avoid potential double frees with the values.
* MFC r314245:ngie2017-03-271-3/+6
| | | | | | | | | | Fill MK_LIBTHR as far as lib/libthr is concerned There are other areas of the tree that will need to be evaluated for sanity if they're supposed to be conditionally compiled out of the build/install, like libzpool Relnotes: yes (this might break someone's system if have the knob set)
* MFC r315641,r315642:ngie2017-03-271-2/+4
| | | | | | | | | | | | | r315641: bsnmp: don't leak snmp_client.fd in open_client_udp(..) on connect(2) failure r315642: bsnmp: explicitly test the return value for open_client_{local,udp} in snmp_open(..) open_client_* returns -1 on failure; 0 on success. Ensure that the return value is 0 -- otherwise exit snmp_open(..).
* MFC r315690:ngie2017-03-271-4/+4
| | | | Delete trailing whitespace (no functional change)
* MFC r315595,r315603:ngie2017-03-272-2/+1
| | | | | | | | | | | | | | | | | | | | | | | r315595: Remove a commented out line before kvm_getprocs(3) The commented out return value for kvm_getprocs(3) was misleading -- the uncommented line is correct. No content change r315603: kvm_close(3): return `error` instead of blindly returning `0` `error` is the accumulated error from previous close(2) calls. This bug has been present since the libcall's import from 4.4BSD Lite (r1573). Noticed by: vangyzen (D10022) Relnotes: yes
* MFC 315229: Remove remnant of r315163.mav2017-03-271-1/+0
|
* MFC 315529kp2017-03-261-0/+3
| | | | | | | | | | | | | | | | | | pf: Fix rule evaluation after inet6 route-to In pf_route6() we re-run the ruleset with PF_FWD if the packet goes out of a different interface. pf_test6() needs to know that the packet was forwarded (in case it needs to refragment so it knows whether to call ip6_output() or ip6_forward()). This lead pf_test6() to try to evaluate rules against the PF_FWD direction, which isn't supported, so it needs to treat PF_FWD as PF_OUT. Once fwdir is set correctly the correct output/forward function will be called. PR: 217883 Submitted by: Kajetan Staszkiewicz Sponsored by: InnoGames GmbH
* MFC r315161: Try to slight untangle I/O and loop status handling.mav2017-03-263-50/+14
|
* MFC r315160: Remove code for unsupported FreeBSD versions.mav2017-03-264-52/+1
|
* MFC r315163: Remove strange config_intrhook_establish() magic.mav2017-03-262-46/+0
| | | | | Interrupts are enabled as part of chip reset just during driver attach. Later "enabling" of already enabled interrupts is useless.
* MFC r315588:kib2017-03-261-2/+3
| | | | Update the list of cpudev ioctls which require write access.
* Synchronize libcxxrt in stable/10 with stable/11.dim2017-03-257-31/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MFC r284553 (by emaste): Update libcxxrt upgrade instructions The typeinfo file no longer exists upstream. MFC r297299: Compile libcxxrt as C++11, since it is only really used in combination with libc++, which is also C++11. Also change one _Static_assert (which is really C11) back into static_assert, like upstream. This should help when compiling libcxxrt with newer versions of gcc, which refuse to recognize any form of static assertions, if not compiling for C++11 or higher. While here, add -nostdinc++ to CFLAGS, to prevent picking up any C++ headers outside the source tree. MFC r299144: Import libcxxrt master 516a65c109eb0a01e5e95fbef455eb3215135cef. Interesting fixes: 3adaa2e Fix _Unwind_Exception cleanup functions 286776c Check exception cleanup function ptr before calling edda626 Correct exception specifications on new and delete operators MFC r303157 (by emaste): libcxxrt: add padding in __cxa_allocate_* to fix alignment The addition of the referenceCount to __cxa_allocate_exception put the unwindHeader at offset 0x58 in __cxa_exception, but it requires 16-byte alignment. In order to avoid changing the current __cxa_exception ABI (and thus breaking its consumers), add explicit padding in the allocation routines (and account for it when freeing). This is intended as a lower-risk change for FreeBSD 11. A "more correct" fix should be prepared for upstream and -CURRENT. Reviewed by: dim Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D7271 MFC r305396: Add _US_ACTION_MASK to libcxxrt's arm-specific unwind header. This value is used in newer versions of compiler-rt.
* MFC r315412, r314852:badger2017-03-252-10/+219
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | r315412: Don't clear p_ptevents on normal SIGKILL delivery The ptrace() user has the option of discarding the signal. In such a case, p_ptevents should not be modified. If the ptrace() user decides to send a SIGKILL, ptevents will be cleared in ptracestop(). procfs events do not have the capability to discard the signal, so continue to clear the mask in that case. r314852: don't stop in issignal() if P_SINGLE_EXIT is set Suppose a traced process is stopped in ptracestop() due to receipt of a SIGSTOP signal, and is awaiting orders from the tracing process on how to handle the signal. Before sending any such orders, the tracing process exits. This should kill the traced process. But suppose a second thread handles the SIGKILL and proceeds to exit1(), calling thread_single(). The first thread will now awaken and will have a chance to check once more if it should go to sleep due to the SIGSTOP. It must not sleep after P_SINGLE_EXIT has been set; this would prevent the SIGKILL from taking effect, leaving a stopped orphan behind after the tracing process dies. Also add new tests for this condition. Sponsored by: Dell EMC
* MFC r313992, r314075, r314118, r315484:badger2017-03-258-101/+1316
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r315484: ptrace_test: eliminate assumption about thread scheduling A couple of the ptrace tests make assumptions about which thread in a multithreaded process will run after a halt. This makes the tests less portable across branches, and susceptible to future breakage. Instead, twiddle thread scheduling and priorities to match the tests' expectation. r314118: Actually fix buildworlds other than i386/amd64/sparc64 after r313992 Disable offending test for platforms without a userspace visible breakpoint(). r314075: Fix world build for archs where __builtin_debugtrap() does not work. The offending code was introduced in r313992. r313992: Defer ptracestop() signals that cannot be delivered immediately When a thread is stopped in ptracestop(), the ptrace(2) user may request a signal be delivered upon resumption of the thread. Heretofore, those signals were discarded unless ptracestop()'s caller was issignal(). Fix this by modifying ptracestop() to queue up signals requested by the ptrace user that will be delivered when possible. Take special care when the signal is SIGKILL (usually generated from a PT_KILL request); no new stop events should be triggered after a PT_KILL. Add a number of tests for the new functionality. Several tests were authored by jhb. PR: 212607 Sponsored by: Dell EMC
* MFC r315745:dim2017-03-251-9/+1
| | | | | | | | | | | | | | | | | | | Cherry-pick libcxxrt commit 8a853717e61d5d55cbdf74d9d0a7545da5d5ff92: Author: David Chisnall <theraven@FreeBSD.org> Date: Wed Mar 22 12:27:08 2017 +0000 Simplify some code. realloc() with a null pointer is equivalent to malloc, so we don't need to handle the two cases independently. Fixes #46 This should help with lang/beignet and other programs, which expect __cxa_demangle(name, NULL, NULL, &status) to return zero in status. PR: 213732
* MFC r315087, r315146:mav2017-03-251-20/+61
| | | | Improve ctl(4) description, including frontends and backends.
* MFC r315084: Increase device openings to tagged maximum.mav2017-03-251-5/+25
| | | | | | | | | | | Some SIMs report much less untagged device openings then tagged ones. Target mode devices are not handled by regular probing routines, and so there is nothing to increase queue size for them to the SIM's maximum. To fix that resize the queue explicitly on ctl periph registration. This radically improves performance of mpt(4) in target mode. Also fetch and report device queue statistics in `ctladm dumpstructs`, since regular way of `camcontrol tags` is not usable in target mode.
* MFC r315082: Allow XPT_GDEV_STATS for UNCONFIGURED devices.mav2017-03-251-29/+18
| | | | | Queue statistics has nothing to do with presence or absence of INQUIRY data, etc. Target mode devices are never configured, but have queues.
* MFC r315361 and r315364: Hide MONITORX/MWAITX from guests.grehan2017-03-253-1/+5
| | | | | | | | | | | | | | r315361 Add the AMD MONITORX/MWAITX feature definition introduced in Bulldozer/Ryzen CPUs. r315364 Hide the AMD MONITORX/MWAITX capability. Otherwise, recent Linux guests will use these instructions, resulting in #UD exceptions since bhyve doesn't implement MONITOR/MWAIT exits. This fixes boot-time hangs in recent Linux guests on Ryzen CPUs (and probably Bulldozer aka AMD FX as well).
* ixgbe(4): Re-add mutex lock call that was dropped in a previous commit.erj2017-03-241-0/+1
| | | | | | PR: 218062 Reported by: Terry Kennedy <terry-freebsd@glaver.org> Sponsored by: Intel Corporation
* Pull in r283944 from upstream libc++ trunk (by Eric Fiselier):dim2017-03-241-28/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix std::pair on FreeBSD Summary: FreeBSD ships an old ABI for std::pair which requires that it have non-trivial copy/move constructors. Currently the non-trivial copy/move is achieved by providing explicit definitions of the constructors. This is problematic because it means the constructors don't SFINAE properly. In order to SFINAE copy/move constructors they have to be explicitly defaulted and hense non-trivial. This patch attempts to provide SFINAE'ing copy/move constructors for std::pair while still making them non-trivial. It does this by adding a base class with a non-trivial copy constructor and then allowing pair's constructors to be generated by the compiler. This also allows the constructors to be constexpr. Reviewers: emaste, theraven, rsmith, dim Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D25389 This should fix building www/chromium 57.0.2987.110 on stable/10 and stable/9 without having to use -D_LIBCPP_TRIVIAL_PAIR_COPY_CTOR=1 (which changes the ABI). Direct commit to stable/10 and stable/9, since head already has libc++ 4.0, which includes this fix.
* Subset of upstream r902 which fixes custom prompts.des2017-03-242-5/+8
| | | | PR: 216172
* MFH (r313974,r314596): open .netrc early in case we want to drop privsdes2017-03-245-55/+77
| | | | | | | | MFH (r314396,r315143): fix a crash caused by an incorrect format string MFH (r314701): fix handling of 416 errors when requesting a range MFH (r315455): fix parsing of IP literals (square brackets) PR: 212065, 217723
* MFC r315453:kib2017-03-241-1/+2
| | | | When clearing altsigstack settings on exec, do it to the right thread.
* MFC r315022: Request change of SIM target role only when it is different.mav2017-03-241-51/+51
| | | | Separate WWNs change into separate request to know what actually failed.
* MFC r315030: Abort all ATIOs and INOTs queued to SIM on LUN disable.mav2017-03-241-22/+45
| | | | | | | Some SIMs may not abort them implicitly, that either fail the LUN disable request or just make us wait for those CCBs forever. With this change I can successfully disable LUNs on mpt(4). For isp(4), which aborts them implicitly, this change should be irrelevant.
* MFC r315025: Switch work_queue from TAILQ to STAILQ.mav2017-03-241-14/+13
| | | | It is mostly FIFO and we don't need random removal there.
* MFC r314365davidcs2017-03-245-87/+319
| | | | | | | | | | | 1. state checks in bxe_tx_mq_start_locked() and bxe_tx_mq_start() to sync threads during interface down or detach. 2. add sysctl to set pause frame parameters 3. increase max segs for TSO packets to BXE_TSO_MAX_SEGMENTS (32) 4. add debug messages for PHY 5. HW LRO support restricted to FreeBSD versions 8.x and above. Submitted by: Vaishali.Kulkarni@cavium.com
* MFC r314814 and r315325.np2017-03-231-8/+27
| | | | | | | | | | | | | r314814: cxgbe/iw_cxgbe: Abort connection if there is an error during c4iw_modify_qp. r315325: cxgbe/iw_cxgbe: Use the socket and not the toepcb to reach for the inpcb. t4_tom detaches the inpcb from the toepcb as soon as the hardware is done with the connection (in final_cpl_received) but the socket is around as long as the cm_id and the rest of iWARP state is. This fixes an intermittent NULL dereference during abort.
* revert r315841, MFC of r315083: not applicable to this branchavg2017-03-231-3/+1
| | | | | | And it broke the build too. Reported by: lwhsu
* MFC r315076: zfs: provide a special vptocnp method for the .zfs vnodeavg2017-03-231-0/+23
|
* add UPDATING entry for r315844, MFC of re-worked .zfs codeavg2017-03-231-0/+6
|
* MFC r314048,r314194: reimplement zfsctl (.zfs) supportavg2017-03-2312-2751/+757
|
* MFC r315083: aacraid: fix build with AACRAID_DEBUG=2avg2017-03-231-1/+3
|
* MFC r315075: trace thread running state when a thread is run for the first timeavg2017-03-232-0/+8
|
* MFC r315074: actually implement proc:::lwp-exit probeavg2017-03-231-0/+1
|
* MFC r314913: MFV r314911: 7867 ARC space accounting leakavg2017-03-231-0/+6
|
* MFC r314912: MFV r314910: 7843 get_clones_stat() is suboptimal for lots of ↵avg2017-03-231-1/+12
| | | | clones
* MFC r314864: firewire/sbp: try to improve locking, plus a few style nitsavg2017-03-231-23/+42
|
* MFC r315067: Partially fix target task management requests handling.mav2017-03-232-109/+125
| | | | | | | | | | | | - XPT_NOTIFY_ACKNOWLEDGE was not handled, causing stuck requests. - XPT_ABORT was not even trying to abort active ATIOs/INOTs. - Initiator's tag was not stored and not used where needed. - List of TM request types needed update. - mpt_scsi_tgt_status() missed some useful debugging. After this change global TM requests, such as reset, should work properly. ABORT TASK (ABTS) requests are still not passes to CTL, that is not good and should be fixed.
* MFC r315004: Add PIM_EXTLUNS support to mpt(4).mav2017-03-232-51/+19
| | | | | Target mode is still limited to 256 LUNs due to the way driver is written, but initiator can now use full 8 byte LUN space.
* MFC r315002: Improve residuals reporting in target mode.mav2017-03-232-2/+7
|
* MFC r314998: Fix FC target mode in mpt(4), broken in multiple ways.mav2017-03-232-92/+51
| | | | | | | | | | | - Not set BufferLength caused receive of empty ATIOs. - CDB length guessing was broken at least for RC16. - mpt_req_untimeout() was called with wrong req parameter. - Sense data reporting was broken in several ways. With this change my LSI7204EP-LC can pass at least basic tests as target. The code is still far from perfect, but finally I found second hw/driver after isp(4) that really can work in CAM target mode.
* MFC r314967: Add support for XPT_GET_SIM_KNOB in FC mode.mav2017-03-232-19/+38
|
* MFC r314968: Report some more data in XPT_PATH_INQ.mav2017-03-232-0/+12
| | | | I am not sure they are used anywhere, but why not.
* MFC r314966: Report FC link speed.mav2017-03-231-3/+21
|
* MFC r311305 (by asomers):mav2017-03-2350-153/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | Always null-terminate ccb_pathinq.(sim_vid|hba_vid|dev_name) The sim_vid, hba_vid, and dev_name fields of struct ccb_pathinq are fixed-length strings. AFAICT the only place they're read is in sbin/camcontrol/camcontrol.c, which assumes they'll be null-terminated. However, the kernel doesn't null-terminate them. A bunch of copy-pasted code uses strncpy to write them, and doesn't guarantee null-termination. For at least 4 drivers (mpr, mps, ciss, and hyperv), the hba_vid field actually overflows. You can see the result by doing "camcontrol negotiate da0 -v". This change null-terminates those fields everywhere they're set in the kernel. It also shortens a few strings to ensure they'll fit within the 16-character field. PR: 215474 Reported by: Coverity CID: 1009997 1010000 1010001 1010002 1010003 1010004 1010005 CID: 1331519 1010006 1215097 1010007 1288967 1010008 1306000 CID: 1211924 1010009 1010010 1010011 1010012 1010013 1010014 CID: 1147190 1010017 1010016 1010018 1216435 1010020 1010021 CID: 1010022 1009666 1018185 1010023 1010025 1010026 1010027 CID: 1010028 1010029 1010030 1010031 1010033 1018186 1018187 CID: 1010035 1010036 1010042 1010041 1010040 1010039
* MFC r308423 (by scottl):mav2017-03-231-0/+8
| | | | | Fix the fallout from r308268 (mpt driver causes endless witness warnings in VMWare and elsewhere) with the precision of a dull, rusty butter knife.
* MFC r303874 (by trasz):mav2017-03-231-4/+0
| | | | Remove NULL check after M_WAITOK allocation from mpt(4).
OpenPOWER on IntegriCloud