summaryrefslogtreecommitdiff
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* - Switch releng/11.3 to -RELEASE.release/11.3.0Glen Barber2019-07-041-1/+1
| | | | | | | | | | | | - Add the anticipated 11.3-RELEASE date to UPDATING. - Set a static __FreeBSD_version. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) Notes: svn path=/releng/11.3/; revision=349754 svn path=/release/11.3.0/; revision=349835; tag=release/11.3.0
* Update UPDATING and bump newvers.shGordon Tetlow2019-07-031-1/+1
| | | | | | | | Approved by: so Approved by: re (implicit) Notes: svn path=/releng/11.3/; revision=349626
* Fix privilege escalation in cd(4) driver.Gordon Tetlow2019-07-035-45/+26
| | | | | | | | | | Approved by: so Approved by: re (implicit) Security: FreeBSD-SA-19:11.cd_ioctl Security: CVE-2019-5602 Notes: svn path=/releng/11.3/; revision=349625
* Update releng/11.3 to RC3 as part of the 11.3-RELEASE cycle.Glen Barber2019-06-281-1/+1
| | | | | | | | Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) Notes: svn path=/releng/11.3/; revision=349480
* Merge from stable/11:Andrey V. Elsukov2019-06-261-0/+1
| | | | | | | | | | | | | | | Fix the uninitialized use of source IPv6 address in NAT64LSN. This code is already refactored in head/, but due to the missing epoch(9) support it is impossible to merge. So, it is direct commit to stable/11. Reported by: Patrick M. Hausen <hausen punkt de> Tested by: Patrick M. Hausen <hausen punkt de> Approved by: re (kib, gjb) Notes: svn path=/releng/11.3/; revision=349429
* Update releng/11.3 to RC2 as part of the 11.3-RELEASE cycle.Glen Barber2019-06-211-1/+1
| | | | | | | | Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Notes: svn path=/releng/11.3/; revision=349252
* MFS r349163: ixl(4)/ixlv(4): Update Intel XL710 PF and VF drivers to ↵Eric Joyner2019-06-1937-1124/+2342
| | | | | | | | | | | | | | | | | | | | | | | | | | | ixl-1.11.9 and ixlv-1.5.8 Update the legacy (non-iflib) drivers in stable/11 with recent changes from the Intel out-of-tree version. Major changes: - Support for new BASE-T device with additional link speeds (2.5G and 5G) and EEE - Additional I2C access methods backported from ixl-iflib - FW LLDP Agent control with sysctl added for X722 devices (this already existed for 710 devices) - MAC/VLAN filters handling has been refactored - Building and loading if_ixlv as a KLD has been fixed This commit is not from CURRENT since the driver in 12/13 uses iflib, and the decision was made to not use iflib in FreeBSD 11 releases. Submitted by: Krzysztof Galazka <krzysztof.galazka@intel.com> Approved by: re@ (gjb@) Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D20290 Notes: svn path=/releng/11.3/; revision=349181
* Copy stable/11@r349022 to releng/11.3 as part of the 11.3-RELEASEGlen Barber2019-06-142-2/+2
| | | | | | | | | | | | | | | cycle. Update releng/11.3 from BETA3 to RC1. Switch the default dvd1.iso pkg(8) repository from latest to quarterly. Bump __FreeBSD_version. Prune vestigial svn:mergeinfo from the new branch. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Notes: svn path=/releng/11.3/; revision=349026
* MFC r348682:Andrey V. Elsukov2019-06-121-0/+2
| | | | | | | | | | | | Initialize V_nat64out methods explicitly. It looks like initialization of static variable doesn't work for VIMAGE and this leads to panic. Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348997
* MFC r348667:Cy Schubert2019-06-111-3/+3
| | | | | | | | | | While working on a PR, more are discovered. Remove more #ifdefs missed in r343701. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348892
* MFC r348666:Cy Schubert2019-06-112-58/+24
| | | | | | | | | Clean up #ifdefs from old unsupported releases of FreeBSD. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348891
* MFC r342747 (mmacy): zfsboot: support newer ZFS versionsKyle Evans2019-06-101-3/+12
| | | | | | | | | | | | | | | declare v3 objset size/layout to fix userboot and possibly other loader issues - fix for userboot assertion failure in zfs_dev_close in free due to out of bounds write - fix for zfs_alloc / zfs_free mismatch assertion failure when booting GPT on BIOS Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348867
* MFC r348601:Slava Shwartsman2019-06-101-3/+17
| | | | | | | | | | | | | | | | | Fix prio vs. nonprio tagged traffic in RDMACM In current RDMACM implementation RDMACM server will not find a GID index when the request was prio-tagged and the sever is non prio-tagged and vise-versa. According to 802.1Q-2014, VLAN tagged packets with VLAN id 0 should be considered as untagged. Treat RDMACM request the same. Reviewed by: hselasky, kib Sponsored by: Mellanox Technologies Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348859
* MFC r348631:Hans Petter Selasky2019-06-101-4/+47
| | | | | | | | | | | | | | In usb(4) fix a lost completion event issue towards libusb(3). It may happen if a USB transfer is cancelled that we need to fake a completion event. Implement missing support in ugen_fs_copy_out() to handle this. This fixes issues with webcamd(8) and firefox. Approved by: re (gjb) Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=348855
* MFC r348604:Hans Petter Selasky2019-06-101-13/+13
| | | | | | | | | | | | In xhci(4) there is no stream ID in the completion TRB. Instead iterate all the stream IDs in stream mode to find the matching USB transfer. Approved by: re(kib) Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=348851
* MFC r348575:Cy Schubert2019-06-102-4/+4
| | | | | | | | | | Properly define the fourth argument to ipf_check, the main entry point into ipfilter. A proper definition simplifies dtrace scripts a little. Approved by: re (delphij@) Notes: svn path=/stable/11/; revision=348850
* MFC r348603:Hans Petter Selasky2019-06-091-0/+2
| | | | | | | | | | Make sure the DMA tags get freed in mlx5en(4). Approved by: re (gjb) Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=348830
* MFC r348718:Cy Schubert2019-06-091-1/+1
| | | | | | | | | Whitespace adjustment. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348825
* MFC r348320:Cy Schubert2019-06-083-11/+7
| | | | | | | | | Contuation of r343701, removal of irrelevant #ifdefs. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348822
* MFC r348312:Cy Schubert2019-06-081-3/+3
| | | | | | | | | style(9) Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348821
* MFC r348311:Cy Schubert2019-06-081-5/+5
| | | | | | | | | | Fix indentation and while at it simplfy the code. Reported by: lwhsu@ Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348820
* MFC r348310:Cy Schubert2019-06-081-2/+2
| | | | | | | | | Remove compile-time tests for unsupported versions of FreeBSD. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348819
* Update stable/11 to BETA3 as part of the 11.3-RELEASE cycle.Glen Barber2019-06-071-1/+1
| | | | | | | | Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Notes: svn path=/stable/11/; revision=348765
* MFC 348543: Warn about deprecated features on all major OS versions.John Baldwin2019-06-061-2/+2
| | | | | | | Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348753
* MFC r348065:Allan Jude2019-06-061-12/+15
| | | | | | | | | | | | | | | | | | | | | | | | Correct the way remaining battery life is calculated Previously, if a system had multiple batteries, the remaining life percentage was calculated as the average of each battery's percent remaining. This results in rather incorrect values when you consider the case of the Thinkpad X270 that has a small 3 cell internally battery, and a hot-swappable 9 cell battery that is used first. Battery 0 is at 100%, but battery 1 is at 10%, you do not infact have 55% of your capacity remaining. The new method calculates the percentage based on remaining capacity out of total capacity, giving a much more accurate reading. PR: 229818 Submitted by: Keegan Drake H.P. <kd-dev@pm.me> Sponsored by: Klara Systems Event: Waterloo Hackathon 2019 Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348726
* MFC r348491:Navdeep Parhar2019-06-057-105/+37
| | | | | | | | | | | | | | | | | | | | cxgbe/t4_tom: adjust the hardware receive window to match changes to the receive sockbuf's high water mark. Calculate rx credits on the spot instead of tracking sbused/sb_cc and rx_credits in the toepcb. The previous method worked when the high water mark changed due to SB_AUTOSIZE but not when it was adjusted directly (for example, by the soreserve in nfsrvd_addsock). This fixes a connection hang while running iozone over an NFS mounted share where nfsd's TCP sockets are being handled by t4_tom. Sponsored by: Chelsio Communications Approved by: re@ (gjb@) Notes: svn path=/stable/11/; revision=348704
* MFC 348206,348231,348454: GELI crypto deprecation warnings.John Baldwin2019-06-031-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 348206: Add deprecation warnings for weaker algorithms to geli(4). - Triple DES has been formally deprecated in Kerberos (RFC 8429) and is soon to be deprecated in IPsec (RFC 8221). - Blowfish is deprecated. FreeBSD doesn't support its successor (Twofish). - MD5 is generally considered a weak digest that has known attacks. geli refuses to create new volumes using these algorithms via 'geli init'. It also warns when attaching to existing volumes or creating temporary volumes via 'geli onetime' . The plan is to fully remove support for these algorithms in FreeBSD 13. Note that none of these algorithms have ever been the default algorithm used by geli(8). Users would have had to explicitly select these algorithms when creating volumes in the past. 348231: Correct the argument passed to g_eli_algo2str() 348454: Remove tests for the deprecated algorithms in r348206 The tests are failing because the return value and output have changed, but before test code structure adjusted, removing these test cases help people be able to focus on more important cases. Approved by: re (gjb) Relnotes: yes Notes: svn path=/stable/11/; revision=348588
* MFC r348247:Kenneth D. Merry2019-05-312-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------ r348247 | ken | 2019-05-24 13:58:29 -0400 (Fri, 24 May 2019) | 57 lines Fix FC-Tape bugs caused in part by r345008. The point of r345008 was to reset the Command Reference Number (CRN) in some situations where a device stayed in the topology, but had changed somehow. This can include moving from a switch connection to a direct connection or vice versa, or a device that temporarily goes away and comes back. (e.g. moving to a different switch port) There were a couple of bugs in that change: - We were reporting that a device had not changed whenever the Establish Image Pair bit was not set. That is not quite correct. Instead, if the Establish Image Pair bit stays the same (set or not), the device hasn't changed in that way. - We weren't setting PRLI Word0 in the port database when a new device arrived, so comparisons with the old value for the Establish Image Pair bit weren't really possible. So, make sure PRLI Word0 is set in the port database for new devices. - We were resetting the CRN whenever the Establish Image Pair bit was set for a device, even when the device had stayed the same and the value of the bit hadn't changed. Now, only reset the CRN for devices that have changed, not devices that sayed the same. The result of all of this was that if we had a single FC device on an FC port and it went away and came back, we would wind up correctly resetting the CRN. But, if we had multiple devices connected via a switch, and there was any change in one or more of those devices, all of the devices that stayed the same would also have their CRN values reset. The result, from a user standpoint, is that the tape drives, etc. would all start to time out commands and the initiator would send aborts. sys/dev/isp/isp.c: In isp_pdb_add_update(), look at whether the Establish Image Pair bit has changed as part of the check to determine whether a device is still the same. This was causing erroneous change notifications. Also, when creating a new port database entry, initialize the PRLI Word 0 values. sys/dev/isp/isp_freebsd.c: In isp_async(), in the changed/stayed case, instead of looking at the Establish Image Pair bit to determine whether to reset the CRN, look at the command value. (Changed vs. Stayed.) Only reset the CRN for devices that have changed. ------------------------------------------------------------------------ Sponsored by: Spectra Logic Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348483
* MFC 348205:John Baldwin2019-05-312-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add deprecation warnings for IPsec algorithms deprecated in RFC 8221. All of these algorithms are either explicitly marked MUST NOT, or they are implicitly MUST NOTs by virtue of not being included in IETF's list of protocols at all despite having assignments from IANA. Specifically, this adds warnings for the following ciphers: - des-cbc - blowfish-cbc - cast128-cbc - des-deriv - des-32iv - camellia-cbc Warnings for the following authentication algorithms are also added: - hmac-md5 - keyed-md5 - keyed-sha1 - hmac-ripemd160 Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348482
* MFC r348236:Andrey V. Elsukov2019-05-311-0/+4
| | | | | | | | | | | | | | | Restore IPV6_NEXTHOP option support that seem was partially broken since r286195. Do not forget results of route lookup and initialize rt and ifp pointers. PR: 238098 Submitted by: Masse Nicolas <nicolas.masse at stormshield eu> Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348470
* Update stable/11 to BETA2 as part of the 11.3-RELEASE cycle.Glen Barber2019-05-311-1/+1
| | | | | | | | Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Notes: svn path=/stable/11/; revision=348450
* Unbreak the powerpc, powerpc64, and sparc64 builds.Michael Tuexen2019-05-301-3/+0
| | | | | | | | | The issue was introduced in r348435. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348441
* MFC 347964:John Baldwin2019-05-301-1/+1
| | | | | | | | | Expose the MD_CLEAR capability used by Intel MDS mitigations to guests. Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348437
* MFC r338053:Michael Tuexen2019-05-304-35/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't expose the uptime via the TCP timestamps. The TCP client side or the TCP server side when not using SYN-cookies used the uptime as the TCP timestamp value. This patch uses in all cases an offset, which is the result of a keyed hash function taking the source and destination addresses and port numbers into account. The keyed hash function is the same a used for the initial TSN. The use of VNET_DEFINE_STATIC(u_char, ts_offset_secret[32]); had to be replaced by VNET_DEFINE(u_char, ts_offset_secret[32]); MFC r348290: When an ACK segment as the third message of the three way handshake is received and support for time stamps was negotiated in the SYN/SYNACK exchange, perform the PAWS check and only expand the syn cache entry if the check is passed. Without this check, endpoints may get stuck on the incomplete queue. Reviewed by: jtl@, rrs@ Approved by: re (kib@)) Sponsored by: Netflix, Inc. Differential Revision: https://reviews.freebsd.org/D16636 Differential Revision: https://reviews.freebsd.org/D20374 Notes: svn path=/stable/11/; revision=348435
* MFC r348075:Konstantin Belousov2019-05-293-2/+8
| | | | | | | | | Do not call hw_mds_recalculate() from initializecpu(). Approved by: re (gjb) Notes: svn path=/stable/11/; revision=348362
* MFC: r346714: Add accessor function for vm->maxcpusRodney W. Grimes2019-05-258-58/+86
| | | | | | | | | | | | | | | Replace most VM_MAXCPU constant useses with an accessor function to vm->maxcpus which for now is initialized and kept at the value of VM_MAXCPUS. This is a rework of Fabian Freyer (fabian.freyer_physik.tu-berlin.de) work from D10070 to adjust it for the cpu topology changes that occured in r332298 Approved by: re (kib) Notes: svn path=/stable/11/; revision=348271
* MFC r347244:Xin LI2019-05-2545-0/+21807
| | | | | | | | | | | Move contrib/zlib to sys/contrib/zlib so that we can use it in kernel. This is a prerequisite of unifying kernel zlib instances. Submitted by: Yoshihiro Ota <ota at j.email.ne.jp> Approved by: re (kib) Notes: svn path=/stable/11/; revision=348261
* Update stable/11 to BETA1 as part of the 11.3-RELEASE cycle.Glen Barber2019-05-241-1/+1
| | | | | | | | Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Notes: svn path=/stable/11/; revision=348211
* MFC: r332298,333712,334199,334216,334219 bhyve cpu topologyRodney W. Grimes2019-05-235-16/+94
| | | | | | | Approved by: re (gjb), bde/phk (mentor, implicit) Notes: svn path=/stable/11/; revision=348201
* MFC r347975:Michael Tuexen2019-05-233-50/+35
| | | | | | | | | | | | | | Improve input validation for the IPPROTO_SCTP level socket options SCTP_CONNECT_X and SCTP_CONNECT_X_DELAYED. MFC r347976: Allow sending on demand SCTP HEARTBEATS only in the ESTABLISHED state. This issue was found by running syzkaller. Approved by: re (gjb@) Notes: svn path=/stable/11/; revision=348174
* MFC r347578: tun/tap: Defer clearing if_softc until after if_detachKyle Evans2019-05-222-6/+10
| | | | | | | | | | | | | | | | | | | | | | | (Commit massaged to match stable structure; tun and tap have been merged in head) r346670 added an sx to close a race between the ifioctl handler and interface destruction. Unfortunately, it clears if_softc immediately after the interface is closed, but before if_detach has been invoked. Any time before detachment, an interface that's part of a bridge may still receive traffic that's pushed through tunstart/tunstart_l2 and promptly lead to a panic because if_softc is now NULL. Fix it by deferring the clearing of if_softc until after the interface has detached and thus been removed from the bridge. if_softc still gets cleared in case another thread has already entered the ioctl handler before it's replaced with ifdead_ioctl. Approved by: re (kib) Notes: svn path=/stable/11/; revision=348126
* MFC r329348 (by brooks):Konstantin Belousov2019-05-204-23/+37
| | | | | | | | | | | | | | | Get rid of the requirement to include SysV IPC headers with _KERNEL defined in ipcrm by introducing _WANT_SYSVxxx_INTERNALS defines. MFC r329390 (by lwhsu): Follow r329348 in ipcs for getting rid of the requirement to include SysV IPC headers with _KERNEL. Sponsored by: Mellanox Technologies Approved by: re (gjb) Notes: svn path=/stable/11/; revision=347995
* MFC r339703, r347365, r347703, r347940Brooks Davis2019-05-1817-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r339703: Deprecate a number of less used 10 and 10/100 Ethernet devices. The current deprecated list is: ae, bm, cs, de, dme, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe The list as refined as part of FCP-0101. Per the FCP, devices may be removed from the deprecation list if enough users are found or they are converted to iflib. FCP: https://github.com/freebsd/fcp/blob/master/fcp-0101.md r347365: Update dme(4) to reflect that it will not be removed due to FCP-101. dme(4) is the built-in NIC on a couple non-expandable mips platforms and thus should remain. The FCP has been updated to reflect this fact. Discussed with: imp r347703: FCP-101: ae(4) is sufficently popular to be moved to the keep list. r347940: Remove the notice that ae(4) will be removed in FreeBSD 13. MFC requested by: rgrimes Approved by: re (kib) Notes: svn path=/stable/11/; revision=347962
* MFC r347625:Konstantin Belousov2019-05-171-0/+1
| | | | | | | | | Properly announce MD_CLEAR. Approved by: re (gjb) Notes: svn path=/stable/11/; revision=347947
* MFC r345008:Kenneth D. Merry2019-05-165-3/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------ r345008 | ken | 2019-03-11 10:21:14 -0400 (Mon, 11 Mar 2019) | 59 lines Fix CRN resets in the isp(4) driver in certain situations. The Command Reference Number (CRN) is part of the FC-Tape features that we enable when talking to tape drives. It starts at 1, and goes to 255 and wraps around to 1. There are a number of reset type conditions that result in the CRN getting reset to 1. These are detailed in section 4.10 (table 8) of the FCP-4r02b specification. One of the conditions is when a PRLI (Process Login) is sent by the initiator, and the Establish Image Pair bit is set in Word 0 of the PRLI. Previously, the isp(4) driver core sent a notification via isp_async() that the target had changed or stayed in place, but there was no indication of whether a PRLI was sent and whether the Establish Image Pair bit was set. The result of this was that in some situations, notably switching back and forth between a direct connection and a switch connection to a tape drive, the isp(4) driver would fail to reset the CRN in situations that require it according to the spec. When the CRN isn't reset in a situation that requires it, the tape drive then rejects every subsequent command that is sent to the drive. It is assuming that the commands are being sent out of order. So, modify the isp(4) driver to include Word 0 of the PRLI command when it sends isp_async() notifications of target changes. Look at the Establish Image Pair bit, and reset the CRN if that bit is set. With this change, I am able to switch a tape drive back and forth between a direct connection and a switch connection, and the isp(4) driver resets the CRN when it should. sys/dev/isp_stds.h: Add bit definitions for PRLI Word 0. sys/dev/ispmbox.h: Add PRLI Word 0 to the port database type, isp_pdb_t. sys/dev/ispvar.h Add PRLI Word 0 to fcportdb_t. sys/dev/isp.c: Populate the new prli_word0 parameter in the port database. In isp_pdb_add_update(), add a check to see if the Establish Image Pair bit is set in PRLI Word 0. If it is, then that is an additional reason to create a change notification. sys/dev/isp_freebsd.c: In isp_async(), if the device changed or stayed, look at PRLI Word 0 to see if the Establish Image Pair bit is set. If it is, reset the CRN if we haven't already. Sponsored by: Spectra Logic Differential Revision: https://reviews.freebsd.org/D19472 ------------------------------------------------------------------------ Notes: svn path=/stable/11/; revision=347894
* MFC r347325:Hans Petter Selasky2019-05-166-11/+11
| | | | | | | | | Bump the Mellanox driver version numbers and the FreeBSD version number. Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=347883
* MFC r347381:Michael Tuexen2019-05-163-3/+18
| | | | | | | | | Prevent cwnd to collapse down to 1 MSS after exiting recovery. This is descrined in RFC 6582, which updates RFC 3782. Notes: svn path=/stable/11/; revision=347882
* MFC r347324:Hans Petter Selasky2019-05-163-34/+23
| | | | | | | | | | | | | Make command workqueue persistant in mlx5core. There is no reason to re-create the command workqueue during healthcare. This also fixes an issue where a previous work struct may refer to a destroyed workqueue. Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=347881
* MFC r347323:Hans Petter Selasky2019-05-163-64/+75
| | | | | | | | | | | | | | | | | | | | | | Fix race between driver unload and dumping firmware in mlx5core. Present code uses lock-less accesses to the dump data to prevent top level ioctls from blocking bottom-level call to dump. Unfortunately, this depends on the type stability of the dump data structure, which makes it non-functional during driver teardown. Switch to the mutex locking scheme where top levels use the mutex in the bound regions, while copyouts and drain for completion utilize condvars. The mutex lifetime is guaranteed to be strictly larger than the time interval where driver can initiate dump, and most of the control fields of the old struct mlx5_dump_data are directly embedded into struct mlx5_core_dev. Submitted by: kib@ Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=347880
* MFC r347322:Hans Petter Selasky2019-05-161-0/+3
| | | | | | | | | | Ensure the flowtable rules are not freed twice in mlx5en(4). This can happen when re-loading the driver. Sponsored by: Mellanox Technologies Notes: svn path=/stable/11/; revision=347879
generated by cgit v1.3 (git 2.53.0) at 2026-09-03 22:29:10 +0000